I've published an archetype catalog on our Maven repository. I can see the
catalog when I browse to the repo, and running mvn to generate a project
finds the reference in the catalog:

mvn archetype:generate
-DarchetypeCatalog=http://maven.xnat.org/libs-snapshot-local
...
Choose archetype:
1: http://maven.xnat.org/libs-snapshot-local ->
org.nrg.xnat:modules-archetype (Archetype for an XNAT multi-module project.)
Choose a number or apply filter (format: [groupId:]artifactId, case
sensitive contains): : 1

But once I select the archetype, this fails:

The desired archetype does not exist
(org.nrg.xnat:modules-archetype:1.0.0-SNAPSHOT)

I can tell why: it's not properly prefixing the repo to the URL, i.e. it's
trying to download:

http://maven.xnat.org/org/nrg/xnat/modules-archetype/1.0.0-SNAPSHOT/maven-metadata.xml

When it should be trying to download:

http://maven.xnat.org/libs-snapshot-local/org/nrg/xnat/modules-archetype/1.0.0-SNAPSHOT/maven-metadata.xml

(Actually, that libs-snapshot-local should really just be libs-snapshot, but
for some reason the archetype-catalog.xml won't resolve properly through the
virtual repo but only through the local repo).

Any help on how to get this working properly would be great. We have a
number of archetypes that it would be great to make available to our users,
but until I can get this resolved we can't do that!

--
View this message in context: 
http://forums.jfrog.org/Issue-with-archetype-catalog-and-resolution-tp7355867p7355867.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

Reply via email to