Would changing that type signature automatically add retries for the checksums
when using the wagon transport? If not, what else would need to be done to add
retries? Would that help with the native transport at all?
-Original Message-
From: Michael Osipov
Sent: Friday, May 19, 2023 5:
The Apache Maven team is pleased to announce the release of the Maven
Dependency Plugin version 3.6.0.
https://maven.apache.org/plugins/maven-dependency-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-dependency-plugin
3.6.0
The Apache Maven team is pleased to announce the release of the Maven
Dependency Plugin version 3.6.0.
https://maven.apache.org/plugins/maven-dependency-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-dependency-plugin
3.6.0
The Apache Maven team is pleased to announce the release of the Maven
Checkstyle Plugin, version 3.3.0.
https://maven.apache.org/plugins/maven-checkstyle-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
>maven-checkstyle-plugin
3.3.
Hi,
The vote has passed with the following result:
+1: Slawomir Jaranowski, Sylwester Lachiewicz, Tamás Cservenák,
Guillaume Nodet
PMC quorum: reached
I will promote the artifacts to the central repo, the source release ZIP
file
and add this release the board report.
-
Hi,
The vote has passed with the following result:
+1: Slawomir Jaranowski, Sylwester Lachiewicz, Tamás Cservenák,
Guillaume Nodet
PMC quorum: reached
I will promote the artifacts to the central repo, the source release ZIP
file
and add this release the board report.
-
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
Howdy,
yes, Contextualizable, Startable, Stoppable, etc are all stuff from oldie
Plexus DI that is EOL. Get rid of all these.
Moreover, am really unsure you _really_ needs the container, as IMHO what
you need instead is:
@Inject
Map macroTypes;
and then just grab from that map what you need.
Re
