Update to Maven4 and Resolver2 #28
Conversation
This is WIP and CI will fail as it uses snapshots.
|
@cstamas will there be two MiMas? (Maven4 + Resolver2 and Maven3.9 + Resolver1.9)? Or may I use single MiMa and override the version of Maven+Resolver? |
|
Will do probably "parallel versions": current MIMA 2.x goes with Maven 3.9 and Resolver 1.x, and MIMA 3.x goes with Maven 4.x + Resolver 2.x... (and they should be "source compatible" as much as possible) Given Maven 3.x (and hence Resolver 1.x) are slowly going into "bug fix maintenance only" mode, not much more to expect from there (upcoming 3.9.6 may be last Maven 3), MIMA 2.x branch may also go slowly into "bug fix maintenance only" mode as well. |
|
@grgrzybek See https://github.com/maveniverse/mima/releases/tag/release-3.0.0-alpha-1 It is Java11+ only... or just build from this PR, as it has issues fixed and MIMA built from this PR will work now from Java8+ (using apache, on 11+ jdk transport takes over). |
So, now: java8 uses apache java11+ uses jdk (takes over)
The resolver alpha-4 is on vote, so it will not work on CI
Parent POM 8 CI Maven versions Wrapper Maven version
Fixes #74 Changes: * default cmd is now REPL, and it dumps just minimal headers (not 3 pages of properties), to see all invoke `dump -v` in REPL * when directly command invoked (like `list` or `classpath` it executes and CLI exits) * removed all the redundant outputs, numberings * hence, direct invocations produce merely needed output (scriptable) * removed INFO prefix
|
This PR now offers Resolver 2.0 (staged) APIs with following constratins:
Note: MIMA in standalone mode still "complements" Resolver with Maven 3.9.8 classes, so this MIMA cannot run on special FileSystems like JIMFS is (that will need Maven4 modelsl) |
|
Dropped MIMA CLI, it was already deprecated and replaced with https://github.com/maveniverse/toolbox |
|
Scratch that: this PR is now Maven 4 + Resolver 2 😄 |
|
With this PR this thing as shown in Resolver PR becomes possible: running resolver on custom NIO FileSystem: |
|
Am thinking... I could do something along these lines:
but, this PR at one moment had
and now this PR has
My point: MIMA X could still remain Java 8, but have all the benefits of Resolver 2,x sans the Google JIMFS-feature (as Maven3 models.stuff still use java.io.File and not java.nio.files). And consequence would be (if we neglect the "embedded" case, when MIMA runs embedded in Maven, and can provide only stuff that Maven in which it runs provides), it would make sense for MIMA user to "choose"... like R2/M3 or R2/M4, but these "runtimes" would be Java 8 or Java 17 in this order. OTOH, I'd really just drop history and make a leap toward Maven 4 (and Resolver 2).... these "choices" may just confuse end users... |
This branch contains beginnings of MIMA 3.x that is Maven4 + Resolver2. Note: as Maven4 went Java 17, the maven libraries used here are in Java 17 bytecode, hence MIMA 3.x becomes Java 17 as well.
For compatibility, see #65 (in short, MIMA 2 works with Maven 3 and Maven 4, but MIMA 3 works with Maven 4 ONLY).