Antrun ignores different settings.xml as specified on Maven command line using
-s option.
-----------------------------------------------------------------------------------------
Key: MANTRUN-122
URL: http://jira.codehaus.org/browse/MANTRUN-122
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Affects Versions: 1.3
Reporter: Scott Lavender
I have multiple build environments that each have their own <localRepository>
as defined in separate settings.xml files. At build time I specify which
settings file to be used using the Maven command.
For example:
mvn -s D:\prod\settings.xml clean install
mvn -X -s D:\test\settings.xml clean install
In either case, the entire build process uses the <localRepository> as defined
in the settings. The problem occurs when the Antrun plugin is invoked, it is
unable to resolve some of the artifacts that were just built and published to
the specified local repository.
I have determined that the Antrun plugin is ignoring the settings file being
specified, and looks to the root settings.xml in the Maven installation instead
( apache-maven-2.0.9\conf\settings.xml). I had initially setup this file, but
no longer maintain my settings there. Instead, I have multiple settings files,
one per product build environment.
Shouldn't the Antrun plugin honor the specified settings.xml values?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
