[ARCHETYPE-59] archetype plugin doesn't use private plugin repository configured in <MAVEN-HOME>/conf/settings.xml

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0-alpha-4
• Component/s: Archetypes
• Environment: windows xp; jdk 1.5.0_09-b01
• Assignee: Unassigned
• Reporter: Martin Testrot
• Created: 03/Nov/06 10:19
• Updated: 03/Jun/08 14:09
• Resolved: 03/Jun/08 14:09

Description

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>
...

Issue Links

• duplicates: ARCHETYPE-1 cannot create project based on archetype that is not in cetral repository
• is related to: MNG-3099 Profiles ignored when working with non-projects (such as archetype:create)