[
http://jira.codehaus.org/browse/ARCHETYPE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated ARCHETYPE-76:
-----------------------------------
After looking the code this is definitlely archetype specific and specific to
any mojo using resolution capabilties that are not done in the same way that
Maven does it. If you look up the artifact resolver, or downloader, without
initializings the WagonManager then there will be no meshing of the
settings.xml. I'll make a more general issue for this.
> Profiles ignored when working with non-projects (such as archetype:create)
> --------------------------------------------------------------------------
>
> Key: ARCHETYPE-76
> URL: http://jira.codehaus.org/browse/ARCHETYPE-76
> Project: Maven Archetype
> Issue Type: Bug
> Reporter: Joakim Erdfelt
> Assignee: John Casey
> Priority: Blocker
> Attachments: MNG-2261-2.patch, MNG-2261.patch
>
>
> Several conditions have to be met to show this bug.
> 1) Be in an environment that does not have access to repo1.maven.org, (such
> as a corporate environment)
> 2) Have no content in your local repository (a fresh install of maven 2.0.4)
> 3) Attempt to use a plugin that has no project requirement (such as
> archetype:create)
> The plugin fails because access to repo1.maven.org cannot be accessed.
> Recommended solution:
> Create a settings.xml profile that changes the location of the 'central'
> repository to point to an internal resource (such as a maven-proxy
> installation).
> <settings>
> <profiles>
> <profile>
> <id>use_internal</id>
> <repositories>
> <repository>
> <id>central</id>
> <name>Internal Central Repository</name>
> <url>http://repo.internal.com/maven2</url>
> <releases>
> <enabled>true</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> </repository>
> </repositories>
> <pluginRepositories>
> <pluginRepository>
> <id>central</id>
> <name>Internal Central Repository</name>
> <url>http://repo.internal.com/maven2</url>
> <releases>
> <enabled>true</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> </pluginRepository>
> </pluginRepositories>
> </profile>
> </profiles>
> <activeProfiles>
> <activeProfile>use_internal</activeProfile>
> </activeProfiles>
> </settings>
> Try again.
> Still fails.
> The reason is that the default behaviour for non-project execution is to use
> the maven super pom, however there is a bug with that flow that does not
> allow for the merging of the settings.xml profiles.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
