SNAPSHOTS are built for this use case. As long as B is in SNAPSHOT mode, A
can continue pulling the latest.
Cheers,
Paul
On Fri, May 9, 2014 at 9:02 AM, James Green wrote:
> 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 n
Hi James,
> 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?
For B to query A at *runtime* of B: embed your build numbers
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 pro
possible ideas:
1. use templating-maven-plugin to copy resource across
2. place the resource into a file and deploy/install as a classifier to be
consumed by B using maven-dependency-plugin
-D
On Fri, May 9, 2014 at 7:02 AM, James Green wrote:
> I have two projects - A and B. B depends on A.
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 q
