[
https://issues.apache.org/jira/browse/ARCHETYPE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933330#comment-15933330
]
Robert Scholte commented on ARCHETYPE-520:
------------------------------------------
I'm working on some new features to the [mock repository
manager|https://github.com/mojohaus/mrm] to have an isolated environment which
works for archetype as well.
If you want to test right now: install mrm yourself
https://git-wip-us.apache.org/repos/asf/maven-archetype.git has a branch called
ARCHETYPE-520. IIUC that contains an integration-test which matches this
usecase.
That should confirm that the mirror is working as expected, unless you can show
me otherwise.
> 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)
