maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Reilly (JIRA)" <>
Subject [jira] Commented: (ARCHETYPE-81) Archetype not downloaded until pom is placed in working dir
Date Sun, 13 Jan 2008 20:30:57 GMT


Tim Reilly commented on ARCHETYPE-81:

This is a known issue in maven not using profile repositories in settings as I've learned
since opening this jira. A close duplicate: ARCHETYPE-89

"A workaround is usable: the archetype:add-repositories goal
that takes -DrepositoryId=central and -DrepositoryUrl= properties
or -Drepositories=central=,company1=

I am tempted to close this issue as a duplicate, but will leave it for now in case any comitters
are tracking from it.

> Archetype not downloaded until pom is placed in working dir
> -----------------------------------------------------------
>                 Key: ARCHETYPE-81
>                 URL:
>             Project: Maven Archetype
>          Issue Type: Bug
>          Components: Plugin
>    Affects Versions: 1.0-alpha-4
>            Reporter: Tim Reilly
> 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:
For more information on JIRA, see:


View raw message