[
https://jira.codehaus.org/browse/ARCHETYPE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316032#comment-316032
]
Chris Feldhacker commented on ARCHETYPE-358:
--------------------------------------------
Based on my limited digging and Maven plugin knowledge:
I think fixing this is tough (well, it involves a difficult decision) because
there appears to be a design mismatch in how the archetype plugin operates and
how Maven itself operates. Maven operates based on a LIST of remote
repositories: the user may or may not use central, and all servers are filtered
through the mirrors list to arrive at a final list of remote repositories.
However, in the final remote repository list, knowledge of which repository
maps to central (if any) is lost.
The archetype plugin is hard-coded to look at exactly one remote repository,
central. There's no good way to resolve or map central to some other
repository (not without some bad hacking) -- exactly which remote repository
from the list should map to central is unknown.
So I think the ultimate question is: Should the archetype plugin really be
hard-coded to look directly at one repository, central? Why not utilize the
list of remote repositories that core Maven already provides (already filtered
through the mirrors), searching each one by one?
> Following mirror configuration from settings.xml
> ------------------------------------------------
>
> Key: ARCHETYPE-358
> URL: https://jira.codehaus.org/browse/ARCHETYPE-358
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator, Plugin
> Affects Versions: 2.1
> Reporter: Grégory Joseph
>
> It looks like the current snapshot of the plugin does not follow the mirror
> configuration from my settings.xml when I do {{mvn archetype:generate}}. I
> would expect it to grab the catalog from
> {{http://nexus.magnolia-cms.com/content/groups/all/archetype-catalog.xml}}
> instead of the central one.
--
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
