[ http://jira.codehaus.org/browse/ARCHETYPE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152182#action_152182 ]

Raphaël Piéroni commented on ARCHETYPE-81:
------------------------------------------

Hi Tim,

could you please try with the new archetype:generate goal using
the 2.0-alpha-4 version of the plugin, to see if it is not to be closed
by obsolescence.

> Archetype not downloaded until pom is placed in working dir
> -----------------------------------------------------------
>
>           Key: ARCHETYPE-81
>           URL: http://jira.codehaus.org/browse/ARCHETYPE-81
>         Project: Maven Archetype
>       Issue Type: Bug
>       Components: Plugin
>   Affects Versions: 1.0-alpha-4
>        Reporter: Tim Reilly
>         Fix For: 2.0-alpha-5
>
>
> Our archetype is hosted internally in the company repository.
> Our settings.xml contains profiles with the internal repository locations.
> I mkdir C:\temp\archtest
> I execute mvn archetype:create -D.... etc
> I get "could not download archetype ... from central
> Next I put a valid pom.xml in the working dir
> I execute mvn archetype:create -D etc
> I get an expected error since the directory is not empty, but now if I check my local repository the archetype is downloaded from the company repository. !! Why wasn't it found until a pom.xml is in the directory?
> Now I delete the pom.xml
> Now I can build sucessfully.
> It would appear the profiles where we define our repositories are not being used until the pom.xml is available. But even mvn -P archetype:create doesn't resolve the issue.

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