[
http://jira.codehaus.org/browse/MNG-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MNG-4278:
----------------------------
Fix Version/s: 2.x
> Allow wildcard in server id in settings.xml
> -------------------------------------------
>
> Key: MNG-4278
> URL: http://jira.codehaus.org/browse/MNG-4278
> Project: Maven 2
> Issue Type: New Feature
> Components: Settings
> Affects Versions: 2.2.0
> Reporter: Julien HENRY
> Fix For: 2.x
>
>
> In my company each project has a separate repository for deploying their
> artifacts (we are using Archiva).
> One developer may work on several projects, and also the integration platform
> (Continuum) must be able to deploy on all repositories.
> Currently I have to add in settings.xml
> {code}
> <server>
> <id>mycompany.project1Id.release</id>
> <username>userId</username>
> <password>xxxxxxx</password>
> </server>
> <server>
> <id>mycompany.project2Id.release</id>
> <username>userId</username>
> <password>xxxxxxx</password>
> </server>
> <server>
> <id>mycompany.project1Id.snapshots</id>
> <username>userId</username>
> <password>xxxxxxx</password>
> </server>
> <server>
> <id>mycompany.project2Id.snapshots</id>
> <username>userId</username>
> <password>xxxxxxx</password>
> </server>
> ... (repeat for every projects)
> {code}
> Where userId and password are always the same.
> It would be great to allow:
> {code}
> <server>
> <id>mycompany.*.*</id>
> <username>userId</username>
> <password>xxxxxxx</password>
> </server>
> {code}
> in settings.xml.
> In case there are several matches for a repositoryId, I think it is better to
> raise an error.
--
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
