[
https://jira.codehaus.org/browse/ARCHETYPE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Feldhacker updated ARCHETYPE-358:
---------------------------------------
Attachment: patch.txt
Attached is a patch for the DefaultArchetypeSelector class.
A new dependency on "org.apache.maven:maven-compat:3.0.4" is needed in order to
reuse existing Mirror processing logic.
The patch trades a hard-coded URL to central (which is bad) with a hard-coded
server id of "central" (which is also bad). Not an ideal solution, but
certainly no worse off than today...
Unfortunately, the getMirrors() method of the existing
ArchetypeGenerationRequest argument returns an empty list of Mirrors and I
don't know why or what the proper way would be to resolve it. Perhaps if
somebody could jump in and solve the other half of this puzzle, we could get a
workable solution...
> 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
> Attachments: patch.txt
>
>
> 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
