Hi, I'm looking for advice to solve what I figure must be a fairly common problem. I have a collection of libraries being built as Maven projects on a Jenkins server. Some libraries depend on each other, but mainly they're used in other, larger projects (possibly on other CI servers).
I want the library projects that depend on each other to build against the latest versions of one another. But for the larger projects, I need to be able to lock library versions down at some point by making releases of the libraries I use. Let's say I have four library projects: - A, latest version 1.1-SNAPSHOT - B, latest version 2.2-SNAPSHOT - depends on A 1.1-SNAPSHOT - C, latest version 3.3-SNAPSHOT - depends on A 1.1-SNAPSHOT - D, latest version 4.4-SNAPSHOT - depends on C 3.3-SNAPSHOT I want to release D 4.4, and I don't want any snapshots in the transitive dependencies, so I need to release A and C, too. Ideally, after the release, the libraries would go back to pointing at one another's next snapshot releases. - A, latest version 1.2-SNAPSHOT - B, latest version 2.2-SNAPSHOT - depends on A 1.2-SNAPSHOT - C, 3.3 depends on A 1.2, 3.4-SNAPSHOT depends on A 1.2-SNAPSHOT - D, 4.4 depends on C 3.3, 4.5-SNAPSHOT depends on C 3.4-SNAPSHOT I guess it's kind of like if I did the first half of a mvn release:prepare in A, C, and D; updated C and D to use the latest version of A; built all of them; then did the second half of mvn release:prepare to go to a new SNAPSHOT version. Is anyone using a similar workflow with Artifactory and/or Jenkins? Thanks, Mike ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
