[
https://issues.apache.org/jira/browse/ARCHETYPE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049456#comment-15049456
]
Stefan Hacker commented on ARCHETYPE-283:
-----------------------------------------
This issue should be reopened. The bug still exists in current versions and is
quite annoying if you don't use the default maven repository location.
> archetype:generate does not use <localRepository> in settings.xml when
> looking for archetype-catalog.xml
> --------------------------------------------------------------------------------------------------------
>
> Key: ARCHETYPE-283
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-283
> Project: Maven Archetype
> Issue Type: Bug
> Affects Versions: 2.0-alpha-4
> Environment: Windows XP, Maven 2.2.1, maven-archetype-plugin
> 2.0-alpha4
> Reporter: ChristopherC
>
> 'mvn archetype:generate -DarchetypeCatalog=local' always looks in
> ~/.m2/archetype-catalog.xml i.e. it will always look in the
> USER_HOME/archetype-catalog.xml regardless of whether the local repository
> location has been overridden in the settings.xml.
> You can verify this by deleting your archetype-catalog.xml in your home
> directory and creating a new one in a different directory - which you then
> specify in settings.xml e.g.:
> <localRepository>D:\differentrepo</localRepository>
> This will not pick up the archetype when running 'mvn archetype:generate
> -DarchetypeCatalog=local'. Now copy a valid archetype catalog to your home
> directory e.g. ~/.m2/archetype-catalog.xml and run 'mvn archetype:generate
> -DarchetypeCatalog=local' and you will see it is not using the
> localRepository from the settings.xml but somewhere it is hardcoded to use
> the user's home directory /.m2/.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
