What I've done over the last few years is use IVY style repositories. That lets you store SEVERAL artifacts for a module in a repository. Use Gradle to save to the repo and retrieve. Don't mess with all those little IVY.xml files. It works great this way. You save upstream artifacts into the repository that downstream builds can use. Also, with Gradle, you can easily rename the artifact after downloading. This is useful if you save a static lib or shared object (.so or .dll) in Artifactory. The version goes into the artifact name as per Java naming conventions, but you don't want it in the retrieved artifact that your project is linking against. Just string out the version as you download in Gradle.
There is not standard way of artifact manage yet for C++ projects, but this has worked. -- View this message in context: http://forums.jfrog.org/How-to-deploy-c-include-lib-filesystem-artifacts-tp7580913p7581000.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Artifactory-users mailing list Artifactory-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/artifactory-users
