1

I have an aggregator pom and two modules.

Module two is dependant on module one.

If I add dependency xyz to module one, module two will inherit it and doesn't need its own separate dependency xyz.

So I can code against xyz in module two if I either set up my IDE to use the poms in the project, or I build and install module one into my local repo.

But then when I commit the changes to git and the CI server runs the tests, it falls over because it picks up the old snapshot of module one from its local repo, which doesn't have the new dependency.

What is the correct approach to solving this on the CI server?

It seems I could force the CI test run to do local installs first, but that seems clunky.

Is there another way to instruct maven to use the latest poms and not the local repo when running aggregator jobs?

Adam
  • 5,215
  • 5
  • 51
  • 90
  • Sounds like you need to have a multi module build which contains both of your projects and handles that case well. Than you only need to build one project which contains two modules with the appropriate dependencies... – khmarbaise Mar 31 '17 at 13:05
  • Do you mean I should put the xyz dependency into the parent pom? – Adam Mar 31 '17 at 14:17
  • [`mvn -U`](http://stackoverflow.com/a/9697970/2646526)? – heenenee Apr 02 '17 at 09:18

0 Answers0