I'm using Artifactory as a Yum repo for RPM's Some of these contain WAR and JAR files. Is there a way to get Artifactory to expose the dependencies of these so tools like Gradle can resolve a dependency to an RPM as a dependency to the contained Jars or wars, Similarly can War files containing Jars declare their contents and dependencies
Example: if I build a Java library that has a dependency on commons-3.0.jar, and that library is part of a servlet packaged as a WAR file running in Tomcat version x.y And Tomcat x.y is accessible as an RPM which contains Jar files as well as dependencies on other RPMs (like apache-commons.rpm) that have jar files. Is it possible for tools like Gradle or Maven to figure this out so they dont pull in commons-3.0.jar when building the WAR file. I know how to explicitly exclude 'provided' jars ... but not how to expose the fact that they exist but are hidden in a RPM or WAR file or dependant RPM or WAR. Would a POM file associated with the build associated with the RPM be recognized and used by Maven or Gradle ? If I 'exploded' the RPM and dependencies ahead of time and imported them to Artifactory would that help ? Or is this beyond the scope of these tools? -- View this message in context: http://forums.jfrog.org/POM-files-for-WAR-and-RPM-s-tp7580431.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
