libcommons-lang3-java FTBFS due to circular build-dep (multiple versions in classpath)

[Tiago Stürmer Daitx]

maven relies on surefire for running tests and surefire depends on libcommons-lang3-java. So whenever libcommons-lang3-java is updated there are 2 versions in the classpath during the testing: the old version in the deb package from surefire's dependency and the new version that was just build. Unfortunately the old version takes precedence in maven/surefire's classpath, thus any test that relies in the new features/classes/interfaces/methods will fail.

This circular build dependency can only be broken by disabling testing for any libcommons-lang3-java update that also modifies the tests - I haven't found a way to force surefire/maven to load and use only the new version under test (or, in other words, to prevent it from loading/using the old classes).

The easiest way to skip the tests is by adding "maven.test.skip=true" to debian/maven.properties [1].

References:
[1] https://wiki.debian.org/Java/MavenBuilder#line-87

[Tiago Stürmer Daitx (tdaitx)]

attaching debdiff that prevents tests from being run during the build

[Launchpad Janitor (janitor)]

This bug was fixed in the package libcommons-lang3-java - 3.7-1ubuntu2

---------------
libcommons-lang3-java (3.7-1ubuntu2) cosmic; urgency=medium

  * Re-enable tests now that we're bootstrapped.

 -- Steve Langasek <email address hidden> Thu, 23 Aug 2018 20:57:08 -0700