It's an Artifactory limitation (current - Artifactory 2.1.3) You are trying to deploy in the libs-snapshots-local Artifactory repository. By default, this above snapshot repository handles only SNAPSHOT artifacts. Firstly, the Ivy revision must contain the SNAPSHOT keyword (it's your case). Then, Artifactory interprets artifacts like Maven artifacts. It doesn't support your Ivy pattern [organisation]/[module]/[revision]/[artifact]-[revision] with a distinction of [module] and [artifact].
For example, if you push an artifact with the following request PUT /artifactory/libs-snapshots-local/org1/module1/1.0-SNAPSHOT/artifact1-1.0-SNAPSHOT.jar HTTP/1.1 against the following resolver pattern [module]/[revision]/[artifact]-[revision].[ext] Artifactory handles the artifact like this: GroupId:org1 ArtifactId:module1 Version: 1.0 Artifactory supports only the following Maven pattern [organisation]/[module]/[revision]/[module]-[revision].[ext] In your case, you get spyglass-1.2.0-SNAPSHOT.jar where spyglass is your organisation identifier. Conclusion: In my opinion, it's an important Artifactory limitation. The start of the Ivy support is good but Artifactory is designed on a Maven approach. -- View this message in context: http://old.nabble.com/Ivy-Publishing-Wrong-Name-to-Artifactory-tp24902518p27313682.html Sent from the Artifactory-Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
