CODEWITHSUNDEEP
javamaven-2hudson
Cristian Vrabie
Cristian Vrabie

Reputation: 4068

Hudson build is using old jars

Hey guys. So I have in Hudson 2 Java/Maven/SVN projects. Let's call them A and B. B depends on A. I sometimes commit code for them simultaneously. Hudson is smart enough to queue the build of B until the build for A is done. However when it does build B it uses an older build (jar). Sometimes several builds/days old. Then B fails because of unknown symbols (new classes/methods in A). I tried to wipe workspace and order a build manually. Same thing. The older build is used. What can I do to force Hudson to use the latest jars build by itself. I haven't tried deleting all previous builds yet but seems an extreme solution. Hopefully it won't be required.

Upvotes: 1

Views: 525

Answers (2)

John Vint
John Vint

Reputation: 40266

If you have your dependent artifacts as snapshots (which you should be) consider setting the maven goal to 

clean deploy -U

This forces maven to update all snapshots.

Upvotes: 1

Peter Lawrey
Peter Lawrey

Reputation: 533870

If you are using maven for your builds are you using the deploy or install targets? If so you should be able to look at the logs and see that the jar in the repository is being updated. If it is up to date, then your pom.xml configuration is likely to be incorrect.

Upvotes: 1

Related Questions