maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bulent Erdemir (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-2261) Profiles ignored when working with non-projects (such as archetype:create)
Date Sat, 20 Jan 2007 22:44:10 GMT
    [ http://jira.codehaus.org/browse/MNG-2261?page=comments#action_85551 ] 
            
Bulent Erdemir commented on MNG-2261:
-------------------------------------

Hi,

I checked out the trunk, compiled, assembled and installed. And tried to execute archetype:create
but it still won't honor the global settings.xml file. Am I missing something ? 

Note: When I compiled and assembled, maven-2.0.6-SNAPSHOT-bin.zip is created and I used this
for testing.

Does any one has any comments on this ? 

Bulent Erdemir


> Profiles ignored when working with non-projects (such as archetype:create)
> --------------------------------------------------------------------------
>
>                 Key: MNG-2261
>                 URL: http://jira.codehaus.org/browse/MNG-2261
>             Project: Maven 2
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.0.4
>            Reporter: Joakim Erdfelt
>         Assigned To: John Casey
>            Priority: Blocker
>             Fix For: 2.0.5
>
>         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

        

Mime
View raw message