1

I have 2 maven projects let's say A and B. We have used Jenkins for build and deployment purpose. A having dependency over B.

I have an issue over here, whenever I changed something in A only and build it using jenkins, each time I have to build B first otherwise while running the system, Application throws exception like "500 method doesn't found" and the method belongs to B.

How can I resolve this issue?

alexandresaiz
  • 2,678
  • 7
  • 29
  • 40
Jay Patel
  • 144
  • 8
  • possible duplicate of http://stackoverflow.com/questions/7362858/maven-dependency-problem-when-jenkins-builds-the-project?rq=1? – gar Sep 25 '15 at 09:10
  • @gar : I have checked the version number and it was provided exactly. I would require to check the generated JAR file of B. But my question is why I have to build B each time If I made changes in A only? Is it necessary? – Jay Patel Sep 25 '15 at 09:38
  • Are the versions snapshots? – gar Sep 25 '15 at 15:40
  • Yes it's a snapshots version. – Jay Patel Sep 29 '15 at 09:00
  • Could be something to do with the updatePolicy on the Jenkins repo. The solution to this question may help: http://stackoverflow.com/questions/19180696/maven-not-using-local-repository – gar Sep 29 '15 at 09:12

0 Answers0