You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Anders Hammar (JIRA)" <ji...@codehaus.org> on 2013/01/28 15:21:13 UTC

[jira] (ARCHETYPE-426) Improved handling of authenticated repositories when generating a project from an archetype

     [ https://jira.codehaus.org/browse/ARCHETYPE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anders Hammar moved MNG-5427 to ARCHETYPE-426:
----------------------------------------------

           Complexity:   (was: Intermediate)
          Component/s:     (was: Artifacts and Repositories)
                       Plugin
    Affects Version/s:     (was: 3.0.4)
                  Key: ARCHETYPE-426  (was: MNG-5427)
              Project: Maven Archetype  (was: Maven 2 & 3)
    
> Improved handling of authenticated repositories when generating a project from an archetype
> -------------------------------------------------------------------------------------------
>
>                 Key: ARCHETYPE-426
>                 URL: https://jira.codehaus.org/browse/ARCHETYPE-426
>             Project: Maven Archetype
>          Issue Type: Improvement
>          Components: Plugin
>            Reporter: Greg Thomas
>            Priority: Minor
>
> Currently, if you wish to generate a project from an archetype that is held in an authenticated repository, you have to ensure that the server holding the artefact has an id in the format <id>[archetypeArtifactId]-repo</id> (reference: http://maven.apache.org/archetype/maven-archetype-plugin/faq.html).
> This means that if you have half-a-dozen different archetypes in your authenticated repository, you have to have half-a-dozen servers defined in your settings.xml that differ only in their id.
> Instead, it would make more sense if it was possible to supply the server id as an optional parameter, e.g. -DServerId=banana (with associated entry in the archetype-catalog). This could default to [archetypeArtifactId]-repo if not supplied for backward compatibility. 
> That way, the settings.xml file will not fill up with duplicate <server> entries, all of which need modifying each and every time the password is changed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira