So you're suggesting controlling this via version numbers?
Have projectB depend on projectA:1.0.1-SNAP, while projectA is actively being worked on the next
version, say 1.0.2-SNAP? Or something like that?
On 07/23/2015 07:48 PM, Paul Benedict wrote:
It sounds like both your projects are snapshots. So when you build
B-SNAPSHOT you have no idea what's inside of A-SNAPSHOT. If this is
bothersome to you, you can think about releasing milestone versions of A so
that B-SNAPSHOT always has a known/reliable codebase to work with. Perhaps
you want weekly snapshots to be released, for example, but you definitely
want to lock down A's version for B.
Cheers,
Paul
On Thu, Jul 23, 2015 at 9:30 PM, V. Mark Lehky <[email protected]> wrote:
Hello.
I have taken it upon myself to fix our Maven project. :)
Our current situation is that we have about dozen child projects, all tied
together with one parent pom. Everything lives in git (Bitbucket) and is
build by Jenkins. There are several (ugly?) python scripts that package and
deploy the finished product. Further some of the tests need to be build
into a jar and run from command line.
Specifically there are two projects, "projectB" is dependent on
"projectA", and both of these have a lot of activity right now. The team
decided to create one branch in git for work on projectA and a separate
branch for work on projectB; let us call them branchA and branchB.
Jenkins builds both of these branches with 'mvn clean install'.
Subsequently tests are run separately with 'mvn -f projectB/pom.xml test'.
The problem is: during test, I do not know which jars I am getting from
the local m2 repo. Occasionally branchA is build and jars are pushed to the
local repo. Then branchB test phase runs, but grabs jars from the local
repo (branchA) which have different code.
Would appreciate some advice how to move forward so as to minimize or
outright eliminate grabbing the wrong jars from the local repo during the
test phase.
TIA for any advice.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
