Is A released after each built-number change or is it a snapshot? In the snapshot case you can add a snapshot dependency and then see the number in the classpath. Maven will find the latest updates. If you make a release I guess it is easier to use a built parameter passed by Jenkins to both projects in a Pipeline. (Or to actually commit changes to version control, hard to say without details).
You could also use the versions-plugin to programmatically bump the dependency version in project B and then run a second maven invocation to build it. Gruss Bernd > Am 09.05.2014 um 16:02 schrieb James Green <james.mk.gr...@gmail.com>: > > I have two projects - A and B. B depends on A. > > A is built with a number (call it a build number). B needs to which number > is in A at the time B builds. > > Any ideas how to achieve this without any human intervention? > > FWIW the use case here is that A is software distributed by B (a WAR > archive). A queries B for an updated build number, thus implementing > "automatic updates". I'm trying to automate the setting of this number > across the two projects but I've drawn a blank inside Jenkins for the > moment. > > James --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
