I should have added:
Before I came along, everything got build as jar-with-dependencies. Test code did not live in
src/test, but in src/main; and was, obviously, not run with 'mvn test', but with 'java -cp
...jar-with-dependencies.jar org.junit.runner.JUnitCore ...AllTests'. All of which I thought was
rather brute. Bloatware, but it did work.
Or was I wrong?
On 07/23/2015 07:30 PM, V. Mark Lehky 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]
