maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William Ferguson (JIRA)" <>
Subject [jira] Commented: (ARCHETYPE-59) archetype plugin doesn't use private plugin repository configured in <MAVEN-HOME>/conf/settings.xml
Date Thu, 02 Aug 2007 05:49:13 GMT


William Ferguson commented on ARCHETYPE-59:

The workaround for this is to specify a 'remoteRepositories' property on the command line
pointing to your internal Repository. Eg

mvn archetype:create -DgroupId=com.yarris -DartifactId=foo-project -DarchetypeGroupId=com.yarris.maven
-DarchetypeArtifactId=archetype-standard -DremoteRepositories=

This issues appears to be a duplicate of :

What I don't understand is that
is marked as closed fixed (with no version), but the issue still clearly exists in maven-2.0.7,

Without a real fix for this issue creating projects using archetypes is not really viable.
Ie it becomes almost as easy to copy and paste an existing project and modify ts details that
to use an archetype.
Which is what I thought we are trying to get away from.

> archetype plugin doesn't use private plugin repository configured in <MAVEN-HOME>/conf/settings.xml
> ---------------------------------------------------------------------------------------------------
>                 Key: ARCHETYPE-59
>                 URL:
>             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
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
> 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:
For more information on JIRA, see:


View raw message