Public bug reported: 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 ** Affects: libcommons-lang3-java (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic ftbfs patch ** Tags added: cosmic ftbfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788735 Title: libcommons-lang3-java FTBFS due to circular build-dep (multiple versions in classpath) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcommons-lang3-java/+bug/1788735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
