Bug#903125: exec-maven-plugin: FTBFS in stretch (expected:<[mvn] --version> but was:<['mvn'] --version>)

[Santiago Vila]

Package: src:exec-maven-plugin
Version: 1.1.1+dfsg-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch + security + stretch-proposed-updates
but it failed:

--------------------------------------------------------------------------------
[...]
 debian/rules build-indep
test -x debian/rules
mkdir -p "."
/usr/share/maven-debian-helper/copy-repo.sh /<<BUILDDIR>>/exec-maven-plugin-1.1.1+dfsg/debian
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory
mh_patchpoms -plibmaven-exec-plugin-java --debian-build --keep-pom-version --maven-repo=/<<BUILDDIR>>/exec-maven-plugin-1.1.1+dfsg/debian/maven-repo  --build-no-docs
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to check if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \
	/usr/bin/make -f debian/rules patch-poms; \
fi

[... snipped ...]

testOverrides(org.codehaus.mojo.exec.ExecMojoTest)  Time elapsed: 0.043 sec  <<< FAILURE!
junit.framework.ComparisonFailure: expected:<[mvn] -f pom.xml> but was:<['mvn'] -f pom.xml>
	at junit.framework.Assert.assertEquals(Assert.java:81)
	at junit.framework.Assert.assertEquals(Assert.java:87)
	at org.codehaus.mojo.exec.ExecMojoTest.checkMojo(ExecMojoTest.java:371)
	at org.codehaus.mojo.exec.ExecMojoTest.testOverrides(ExecMojoTest.java:331)

testOverrides3(org.codehaus.mojo.exec.ExecMojoTest)  Time elapsed: 0.035 sec  <<< FAILURE!
junit.framework.ComparisonFailure: expected:<[mvn] --version> but was:<['mvn'] --version>
	at junit.framework.Assert.assertEquals(Assert.java:81)
	at junit.framework.Assert.assertEquals(Assert.java:87)
	at org.codehaus.mojo.exec.ExecMojoTest.checkMojo(ExecMojoTest.java:371)
	at org.codehaus.mojo.exec.ExecMojoTest.testOverrides3(ExecMojoTest.java:340)

Running org.codehaus.mojo.exec.ExecJavaMojoTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.241 sec - in org.codehaus.mojo.exec.ExecJavaMojoTest

Results :

Failed tests: 
  org.codehaus.mojo.exec.ExecMojoTest#testRunOK ComparisonFailure expected:<[mvn...
  org.codehaus.mojo.exec.ExecMojoTest#testRunFailure ComparisonFailure expected:...
  org.codehaus.mojo.exec.ExecMojoTest#testRunError ComparisonFailure expected:<[...
  org.codehaus.mojo.exec.ExecMojoTest#testOverrides ComparisonFailure expected:<...
  org.codehaus.mojo.exec.ExecMojoTest#testOverrides3 ComparisonFailure expected:...

Tests run: 14, Failures: 5, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 14.291 s
[INFO] Finished at: 2018-07-06T13:15:30+00:00
[INFO] Final Memory: 19M/90M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project exec-maven-plugin: There are test failures.
[ERROR] 
[ERROR] Please refer to /<<BUILDDIR>>/exec-maven-plugin-1.1.1+dfsg/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
/usr/share/cdbs/1/class/maven.mk:127: recipe for target 'debian/stamp-maven-check' failed
make: *** [debian/stamp-maven-check] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
--------------------------------------------------------------------------------

The build was made with "dpkg-buildpackage -A" but I guess that's not
relevant at all in this case.

Apparently some build-dependency in security or stretch-proposed-updates
changed behaviour in a way that makes the tests to break, but I'm not
sure a reassign would be a good thing here.

Thanks.