-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
None
Running Maven using the following startup args does not work with the MavenResovler, the new defined settings.xml is not read
mvn install -s settings.xml
[SHRINKRES-8] MavenResolver does not take settings.xml specified on command line into account when resolving repositories
Karel Piwko
added a comment - This can be solved by a maven plugin, e.g. either a support in Surefire itself (see SUREFIRE-790) or a standalone plugin, POC at
https://github.com/kpiwko/resolver-maven-plugin
I'd like the plugin to become a standard part of 2.0.0 distribution.
Karel Piwko
added a comment - This can be solved by a maven plugin, e.g. either a support in Surefire itself (see SUREFIRE-790) or a standalone plugin, POC at
https://github.com/kpiwko/resolver-maven-plugin
I'd like the plugin to become a standard part of 2.0.0 distribution. Karel Piwko
added a comment - MavenResolver is using Aether to resolve artifacts and does not depend on parent Maven process. This means that it can be executed from any environment, not necessarily started by Maven.
I'm not sure if there's a way how to check what spawned Aether and what arguments it got from there.
WDYT?
Karel Piwko
added a comment - MavenResolver is using Aether to resolve artifacts and does not depend on parent Maven process. This means that it can be executed from any environment, not necessarily started by Maven.
I'm not sure if there's a way how to check what spawned Aether and what arguments it got from there.
WDYT? 
It is impossible to get the information from Maven execution directly. There is a Shrinkwrap Resolver Maven plugin, which is a part of the distribution and it allows to retrieve this information.
It was pushed upstream in https://issues.jboss.org/browse/SHRINKRES-21