[
http://jira.codehaus.org/browse/MNG-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jieryn reopened MNG-4759:
-------------------------
For distributed builds which are utilizing clustered continuous integration
(like Hudson), it is quite handy to have all slaves utilizing the same
settings.xml file. The problem then becomes how to reliably get the
settings.xml to slave node without requiring explicit configuration of those
slaves. It would be far easier if I could store a Maven settings.xml file in
some SCM and point to it via standard Maven URI of such a resource.
An example command line invocation might look like:
$ mvn --global-settings
scm:svn:http://repo.acme.com/infrastructure/maven/settings.xml clean install
This would cause Maven to fetch settings.xml from SCM and use it for subsequent
clean and install goal execution. The main issue I'm facing presently is that
dynamically provisioned slave resources do not automatically mirrOf * to our
corporate MRM.
Maven already supports a --global-settings configuration switch, I just would
like it to be enhanced to be more robust in what it accepts.
> Allow --global-settings target arbitrary resources, e.g.
> scm:svn:http://svn.acme.com/infra/trunk/maven/settings.xml
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-4759
> URL: http://jira.codehaus.org/browse/MNG-4759
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Command Line
> Reporter: jieryn
>
--
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
