1

Consider the following scenario:

  1. At t = 0:00, a test suite job A is started on host B using a SNAPSHOT build of library C, executing this test takes more than half an hour
  2. At t = 0:10, a new SNAPSHOT build is generated for library C and deployed to our Maven repository server on host D
  3. At t = 0:20, a second test job E is started on host B, also using a SNAPSHOT build of library C. This run updates the SNAPSHOT in the local Maven repository on host B
  4. At t >= 0:20, job A starts raising java.lang.NoClassDefFoundError errors, because its code was compiled against a different version of library C.

Is there a best-practice on how to handle this issue?

Hoppie
  • 199
  • 2
  • 9
  • Consider using a different local repo for each run: https://stackoverflow.com/questions/6823462/specifying-mavens-local-repository-location-as-a-cli-parameter – Ville Oikarinen Jun 06 '17 at 11:37

0 Answers0