You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/06/13 00:51:15 UTC
[jira] Updated: (MNG-3099) Profiles ignored when working with
non-projects (such as archetype:create)
[ http://jira.codehaus.org/browse/MNG-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3099:
------------------------------
Fix Version/s: (was: 2.1)
> Profiles ignored when working with non-projects (such as archetype:create)
> --------------------------------------------------------------------------
>
> Key: MNG-3099
> URL: http://jira.codehaus.org/browse/MNG-3099
> Project: Maven 2
> Issue Type: Bug
> Reporter: Joakim Erdfelt
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0.9
>
> Attachments: MNG-2261-2.patch, MNG-2261.patch, Plugin-showing-MNG3099.zip
>
>
> 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