maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (ARCHETYPE-426) Improved handling of authenticated repositories when generating a project from an archetype
Date Fri, 16 Mar 2018 22:42:07 GMT

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

Michael Osipov closed ARCHETYPE-426.
------------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If
you think this issue still applies, retest your problem with the most recent version of Maven
and the affected component, reopen and post your results.

> Improved handling of authenticated repositories when generating a project from an archetype
> -------------------------------------------------------------------------------------------
>
>                 Key: ARCHETYPE-426
>                 URL: https://issues.apache.org/jira/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 was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message