[
https://issues.apache.org/jira/browse/ARCHETYPE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931442#comment-15931442
]
Robert Scholte commented on ARCHETYPE-520:
------------------------------------------
I've been working on inproving the set of intregration tests, but the current
SNAPSHOT seems to go to the mirror as expected. Will need to investigate a bit
more.
> Following mirror configuration from settings.xml for downloading archetype
> metadata
> -----------------------------------------------------------------------------------
>
> Key: ARCHETYPE-520
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-520
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 3.0.0
> Reporter: Johannes Siebel
> Attachments: maven-archetype-delay.TXT, settings.xml
>
>
> Since using the maven-archetype-plugin with version 3.0.0 the plugin tries to
> connect to _both_ our internal nexus and to {{http://repo.maven.apache.org}}
> for downloading Maven artifacts used by Archetypes. Since we are using a
> proxy, the generation of the archetype is delayed until the download of the
> Maven artifacts times out.
> We'd expect the archetype to only contact our own artifact repository,
> without trying to connect to {{http://repo.maven.apache.org}} at all.
> I've attached a snippet with the debug output of the archetype:generate goal
> and the configuration of our mirror.
> We assume this problem is related to ARCHETYPE-358.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
