Greg Thomas created MNG-5427: -------------------------------- Summary: Improved handling of authenticated repositories when generating a project from an archetype Key: MNG-5427 URL: https://jira.codehaus.org/browse/MNG-5427 Project: Maven 2 & 3 Issue Type: Improvement Components: Artifacts and Repositories Affects Versions: 3.0.4 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