You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Nelz (JIRA)" <ji...@codehaus.org> on 2007/07/12 03:56:13 UTC
[jira] Commented: (ARCHETYPE-59) archetype plugin doesn't use
private plugin repository configured in /conf/settings.xml
[ http://jira.codehaus.org/browse/ARCHETYPE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102002 ]
Nelz commented on ARCHETYPE-59:
-------------------------------
FYI, this is still happening for me.
WinXP Pro, JDK 1.5.0_11, Maven 2.0.7
Ubuntu 7.04, JDK 1.6.0.00
I saw some traffic on http://jira.codehaus.org/browse/MNG-3099 that this might have been solved in 2.0.7, but I am living proof that it is not...
> archetype plugin doesn't use private plugin repository configured in <MAVEN-HOME>/conf/settings.xml
> ---------------------------------------------------------------------------------------------------
>
> Key: ARCHETYPE-59
> URL: http://jira.codehaus.org/browse/ARCHETYPE-59
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
> Affects Versions: 1.0-alpha-4
> Environment: windows xp
> jdk 1.5.0_09-b01
> Reporter: Martin Testrot
>
> I configured the file <Maven-Home>/conf/settings to use a local, private plugin repository to prevent uncontrolled download from the official central repository at http://repo1.maven.org/maven2. This works fine except in the case I call the archetype plugin (archetype:create). In this case the settings.xml is ignored and all plugins are downloaded from the central repository at maven.org.
> I observed the same when calling mvn help:active-profiles in a directory that doesn't contain a pom.xml file.
> If I place a dummy pom.xml file in this directory the settings.xml are used and everything is fine. But if I use this trick with the archetype plugin the newly created project (creation via archetype) is configured as a child of my dummy pom (pom.xml contains parent section with dummy pom). I the case of a dummy pom this is not intended.
> So i would be nice if you can fix the archtype plugin to use the configured settings.xml. I really would like to use this plugin, because it would help a lot to standardize a common project layout for our developers. This is a majour reason for choosing maven2.
> Greetings,
> Martin
> Here is the relevant section of my settings.xml:
> ...
> <profiles>
> <profile>
> <!-- profile for using private plugin and 3rd party repositories -->
> <id>private-repo</id>
> <pluginRepositories>
> <pluginRepository>
> <!-- repository contains all maven-plugins required to run our build -->
> <id>central</id>
> <name>private plugin repository</name>
> <url>http://localserver/mvn-repos/maven-plugin</url>
> <releases>
> <enabled>true</enabled>
> <updatePolicy>daily</updatePolicy>
> </releases>
> <snapshots>
> <enabled>false</enabled>
> </snapshots>
> </pluginRepository>
> </pluginRepositories>
> </profile>
> </profiles>
>
> <activeProfiles>
> <activeProfile>private-repo</activeProfile>
> </activeProfiles>
> ...
--
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