Doh, just that quickly, I realized that the problem with the repo was set in
the archetype-catalog.xml itself:
<repository>http://maven.xnat.org/libs-snapshot</repository>
I do still have the issue with the archetype-catalog.xml being unresolvable
through the virtual repo libs-snapshot, which is interesting because, as you
can see above, the actual archetype itself is available through the virtual
repo.
Also, it'd be nice if the repo was resolved automatically by de-referencing
the catalog's location, i.e. the catalog at
http://maven.xnat.org/libs-snapshot-local would automatically get that
pathing for the archetype. But that's probably in the maven tool itself, and
difficult to override at the server level (e.g. automatically populate a
<repository> element when the catalog is requested if it's not already
available).
--
View this message in context:
http://forums.jfrog.org/Issue-with-archetype-catalog-and-resolution-tp7355867p7355892.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
