Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: 1.0-alpha-4
-
Fix Version/s: 2.0-alpha-5
-
Component/s: Plugin
-
Labels:None
-
Number of attachments :
Description
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 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=http://repo1.maven.org/maven2 properties
or -Drepositories=central=http://repo1.maven.org/maven2,company1=http://repo1.company.com property"
I am tempted to close this issue as a duplicate, but will leave it for now in case any comitters are tracking from it.