I'm deploying both a .jar and a .pom via REST to Artifactory (successfully), but when I attempt to reference the deployed .jar as a dependency, Maven is unable to resolve it. Other artifacts in the same repository that were uploaded via the GUI work fine, so I'm confident that resolution is failing because of something missing when deploying via REST, perhaps metadata.
The only major difference that I can see between the between artifacts deployed via REST and those deployed via the GUI is that the ones deployed via REST have "Module ID: N/A", e.g. http://forums.jfrog.org/file/n6820781/module.png Is "Module ID" required for Maven to successfully resolve artifacts? If so, how can I set it via REST? Additionally, is there a minimum set of metadata necessary for resolution documented someplace? Thanks, Segphault -- View this message in context: http://forums.jfrog.org/Maven-can-t-resolve-artifacts-deployed-via-REST-tp6820781p6820781.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
