[FTBFS] maven-compiler-plugins fails to build due to hardcoded compiler version

[Tiago Stürmer Daitx]

The maven compiler version 3.6.1 is hardcoded into maven, thus causing a FTBFS when trying to rebuild the maven-compiler-plugin after 3.6.2-1 was synced to the archive.

This causes various maven dependent projects to fail - including maven-compiler-plugin itself

In order to fix this circular dependency, the maven-compiler-plugin needs to:

1) Override the dh_auto_configure to copy maven-compiler-plugin 3.2 repository data over 3.6.1; 3.2 is just a relocate/redirect to 3.6.2, thus we force the build to consider 3.6.1 as 3.6.2, this is only required on the first build, subsequent builds won't need as the next step will do this for us.
2) Use the relocate feature of a pom.xml file to force dependencies on maven-compiler-plugin 3.6.1 to use 3.6.2 instead.

After that first build is done a second one should remove step #1 since the relocate in step #2 will take care of that from there on.

[Tiago Stürmer Daitx (tdaitx)]

Attached debdiff to:
* Copy libmaven-compiler-plugin version 3.2 over 3.6.1 to fix build.
* Relocate libmaven-compiler-plugin version 3.6.1 to version 3.6.2
  to fix future builds for this and all other maven dependent packages.
* Set JAVA_HOME to prevent compiler test failure.
* Patch wrong junit path in compiler test.

[Tiago Stürmer Daitx (tdaitx)]

After building 3.6.2-2ubuntu1 (patch above), the following update should be applied.

* Remove dh_auto_configure override, no longer required after
  the 3.6.1 -> 3.6.2 relocate done in 3.6.2-2ubuntu1.

[Launchpad Janitor (janitor)]

This bug was fixed in the package maven-compiler-plugin - 3.6.2-2ubuntu2

---------------
maven-compiler-plugin (3.6.2-2ubuntu2) artful; urgency=medium

  * Remove dh_auto_configure override, no longer required after
    the 3.6.1 -> 3.6.2 relocate done in 3.6.2-2ubuntu1.

 -- Tiago Stürmer Daitx <email address hidden> Sat, 08 Sep 2017 18:32:01 +0000