Bug#912231: bnd FTBFS with OpenJDK 11

[Markus Koschany]

Hi,

Am 19.12.18 um 22:32 schrieb Emmanuel Bourg:
> Le 29/10/2018 à 23:32, Markus Koschany a écrit :
>> The OpenJDK 11 issue is rather simple to fix, however the build fails
>> later on with this error message, a Gradle issue?
> 
> I've figured out what is causing the second issue, the poms are
> installed into .gradle/daemon/4.4.1/debian/.m2/ instead of debian/.m2/.
> 
> Due to the way gradle-debian-helper 2.0.1 injects its code in the Gradle
> classpath the Gradle daemon is always started, and the daemon uses a
> different working directory (.gradle/daemon/4.4.1/). Since the location
> of the Maven repository where the artifacts are installed is specified
> as a relative path, it's shifted under the daemon working directory and
> maven-repo-helper no longer finds the artifacts at the expected path.
> 
> This can be fixed by setting the repository location with an absolute
> path (the HOME variable in debian/rules).
> 
> Emmanuel Bourg

Thanks for fixing this bug. I believe others will be affected by it too
in the future. Shouldn't that be fixed in gradle-debian-helper instead?
I mean it's not obvious that one has to export HOME now. I have no
immediate solution though.

Regards,

Markus

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20181220/ea5485cd/attachment.sig>