Excellent, thanks. Using the ‘Test Artifact Path Resolution’ I can see where our problem lies in our paths.
Also, we have our repositories configured as maven layout, so we're going to have a bit of bother here as even when we publish with the correct path information it won't clear out our ivy.xml as it's probably looking for a pom. Lessons learnt, time to plan future improvements. -- View this message in context: http://forums.jfrog.org/Delete-Versions-use-with-ivy-published-artifacts-tp7579895p7579897.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
