Am 2023-05-20 um 00:35 schrieb Henning Schmiedehausen:
Hi,
The page on https://maven.apache.org/resolver/maven-3.8.x.html states
that *"Since
version 1.7.0, Maven Resolver requires Java 8 to run and a brand new
default sync context factory has been implemented."*.
Assuming for a moment that Java 8+ is a no-brainer, what does the second
part of that sentence mean? If a plugin would require Java 8+ anyway (or
even Java 11+), would it be possible for a plugin to move past 1.6.x and
still be compatible with Maven 3.8.x or would using any version past 1.6.3
(we are on 1.9.x now) not work with Maven 3.8?
I have a plugin that has resolver api in "provided" scope so it will be
whatever maven will inject into the plugin and the implementation itself is
in compile scope (so it will be bundled with the plugin).
Short version: yes.
First of all, I provide signed artifacts of Maven 3.8.x:
* https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.x-resolver-1.9.x/
* https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.x-resolver-1.8.x/
with just Maven Resolver updated. It just works with 3.8.x
Long answer: As long as your plugin uses the API from 1.6.x it can run
with 3.8.x and above, but if there is any API change and you start to
use it, of course you need my modified version. You can enjoy all
benefits from 1.9.x with 3.8.x. Beware that settings done by Maven 3.9.x
directly to Resolver do not apply here, so the 3.8.x defaults apply,
e.g., transport and stuff.
I will try to produce updated artifacts with Resolver 1.9.10.
I must admit that 3.9.x should have been 3.10.x and 3.8.x moved to 3.9.x
with just the Resolver and Java 8 upgrade, but that ship has sailed :-(
M
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
