By re-reading your mail, I just figured I might have missed your point as
well :)
So yes,:
- declare resolver artifacts you need as "provided"
- stick with resolver api, spi, util (all provided)
and you are on the safe side, whatever Maven you use (naturally from
[3.1-3.999] range, as Maven 3.0 u
Howdy,
as long as your code "play by the rules" (as explained here):
https://maven.apache.org/resolver/api-compatibility.html
we guarantee you binary compatibility when using resolver within Maven.
That said, in your mojo you just inject the reposystem "as usual" (so as
you say in your mail) and
Thank you for the quick response. However, I am not sure that I got what I
needed.
Upgrading/changing maven etc. is a non-starter. This is a plugin (
https://github.com/basepom/dependency-versions-check-maven-plugin/), which
I maintain. It is supposed to be compatible with Maven 3.8.x (older
versi
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 Jav
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 s
