Stuart,
that was very valuable information! Thank you!
I have boldly applied your recommendation and it works in the core
realm:
https://github.com/apache/maven-resolver/commit/2e78944a673ac7267f9d40abdeb4816f00381797#diff-0b6e1366069deb9a8dcbf0126334e47dR65-R69
As for the plugin, I have
Hi,
a new version of the maven-resources-plugin (3.2.0) has been released
recently.
Trying to take advantage of this I added
org.apache.maven.plugins
maven-resources-plugin
3.2.0
org.apache.maven.shared
Thanks John for such a detailed explanation. Few doubts
For release version assuming empty local repo.
> - Build order this time alpha, bravo, charlie
> - Alpha needs A, and Aa is downloaded as it's in central repo and that
> was 1st repo in the order list
When you say central repo is the first
Scratch that - the AetherModule and DefaultServiceLocator are only used by
clients that don't use dependency injection, they're not used by Maven
itself.
The log snippet you posted above shows both SyncContextFactory components
are being bound in the same realm - they are therefore given the
The issue is indeed with AetherModule which is installed by Maven
via MavenAetherModule
This module adds concrete bindings for various Aether components which
cannot be overridden in plugins/extensions.
These bindings will need to be changed to support overriding, I'll create a
patch to show how
