Bug#909905: gradle FTBFS when building with openjdk-11 (needs update to 4.7.0 or upstream patch)

2018-10-01 Thread shirish शिरीष
at bottom :-

On 02/10/2018, Emmanuel Bourg  wrote:
> Le 01/10/2018 à 19:37, shirish शिरीष a écrit :
>
>> So are we going to have gradle 4.8 in either experimental or unstable
>> soonish.
>
> Unfortunately no. Starting with version 4.5 Gradle requires Kotlin, and
> we are nowhere near having Kotlin in Debian. It's more likely we'll
> instead patch Gradle 4.4 and fix the Java 11 incompatibilities.
>
>
>> I'm sure you may have read the freeze time-table which was shared few days
>> ago.
>>
>> It would be nice to have all the components in debian tested etc. well
>> before freeze.
>
> Sure but this won't happen magically, we need more contributors.
>
> Emmanuel Bourg
>

I can help with testing but that's all I can help with :(

I did see in the tracker though that the newer gradle isn't migrating towards
testing due to jgit which I didn't know was a package till I saw it -

tracker.debian.org/gradle

I also saw https://bugs.debian.org/905547 which is a wishlist bug for
getting a new version of jgit also which is one of the blockages of
transitioning to testing.

I am open to testing that as well  . I did see that the recent commits
to jgit-cli and brethen were on 5th august last ,

~/games/eclipse-jgit$ git log
commit 609ea8c723cba1584f75cef8dc8378e9206cd4bd (HEAD -> master,
origin/master, origin/HEAD)
Author: Emmanuel Bourg 
Date:   Thu Aug 16 01:04:37 2018 +0200

Upload to unstable


and that's -

$ apt-cache policy jgit-cli
jgit-cli:
  Installed: (none)
  Candidate: 3.7.1-5
  Version table:
 3.7.1-5 100
100 http://deb.debian.org/debian unstable/main amd64 Packages

Looking forward to testing a new version of jgit assuming of course it
doesn't have
any complexities or additional package requirements as the newer
gradle seems to have.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8



Bug#909905: gradle FTBFS when building with openjdk-11 (needs update to 4.7.0 or upstream patch)

2018-10-01 Thread Tiago Daitx
Updated patch to include the missing DEP-3 headers and to remove the test files.
On Mon, Oct 1, 2018 at 9:52 PM Tiago Daitx  wrote:
>
> I have updated the patch to include 3 additional commits from
> upstream, this fixes the build with openjdk-11 and stops gradle from
> FTBFS.
>
> The last applied patch [1], which actually gets rid of the
> "NoSuchMethodError: sun.misc.Unsafe.defineClass" error, required me to
> remove the kotlin classes and then put the new classes under
> subprojets/base-services/ instead of subprojects/base-services-java9/
> in order to get them to compile - the logic of handling the
> subprojects has been moved to kotlin and I didn't check if there was a
> way to get it working with separated directories under gradle's 4.4
> build structure.
>
> For now I kept the openjdk-11 version check patch as it was
> originally, having the full JEP-223 might actually be a good thing - I
> will let the decision to someone who understands gradle better than I
> do.
>
> Of course, always bootstrap with openjdk-10 first, after that the
> generated binaries are good enough to get it to build with openjdk-11.
>
> [1] 
> debian/patches/use-lookup-instead-of-reflection-on-java-9-3db6e25698705317.patch
>
> On Mon, Oct 1, 2018 at 8:39 PM Emmanuel Bourg  wrote:
> >
> > Le 01/10/2018 à 19:37, shirish शिरीष a écrit :
> >
> > > So are we going to have gradle 4.8 in either experimental or unstable 
> > > soonish.
> >
> > Unfortunately no. Starting with version 4.5 Gradle requires Kotlin, and
> > we are nowhere near having Kotlin in Debian. It's more likely we'll
> > instead patch Gradle 4.4 and fix the Java 11 incompatibilities.
> >
> >
> > > I'm sure you may have read the freeze time-table which was shared few 
> > > days ago.
> > >
> > > It would be nice to have all the components in debian tested etc. well
> > > before freeze.
> >
> > Sure but this won't happen magically, we need more contributors.
> >
> > Emmanuel Bourg
> >
>
>
> --
> Tiago Stürmer Daitx
> Software Engineer
> tiago.da...@canonical.com
>
> PGP Key: 4096R/F5B213BE (hkp://keyserver.ubuntu.com)
> Fingerprint = 45D0 FE5A 8109 1E91 866E  8CA4 1931 8D5E F5B2 13BE



-- 
Tiago Stürmer Daitx
Software Engineer
tiago.da...@canonical.com

PGP Key: 4096R/F5B213BE (hkp://keyserver.ubuntu.com)
Fingerprint = 45D0 FE5A 8109 1E91 866E  8CA4 1931 8D5E F5B2 13BE
diff -Nru gradle-4.4/debian/changelog gradle-4.4/debian/changelog
--- gradle-4.4/debian/changelog	2018-10-01 14:12:33.0 +0100
+++ gradle-4.4/debian/changelog	2018-10-01 20:05:23.0 +0100
@@ -1,3 +1,17 @@
+gradle (4.4-4) UNRELEASED; urgency=medium
+
+  * Enable support for openjdk-11 (Closes: #909905)
+- debian/patches/enable-jdk-11-support-ac15612d41b43c39c.patch:
+  enable support for openjdk-11.
+- d/p/use-lookup-to-invoke-defineclass-java-9-028548460bd929fd.patch:
+  Use Lookup to invoke defineClass on Java 9+.
+- d/p/do-not-use-classLoader-getdefinedpackages-on-java-9-50eababaa25230ab.patch:
+  Don't use ClassLoader.getDefinedPackages() on Java 9.
+- d/p/use-lookup-instead-of-reflection-on-java-9-3db6e25698705317.path:
+  Use Lookup instead of reflection on Java 9+.
+
+ -- Tiago Stürmer Daitx   Mon, 01 Oct 2018 21:12:00 +
+
 gradle (4.4-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru gradle-4.4/debian/patches/do-not-use-classLoader-getdefinedpackages-on-java-9-50eababaa25230ab.patch gradle-4.4/debian/patches/do-not-use-classLoader-getdefinedpackages-on-java-9-50eababaa25230ab.patch
--- gradle-4.4/debian/patches/do-not-use-classLoader-getdefinedpackages-on-java-9-50eababaa25230ab.patch	1970-01-01 01:00:00.0 +0100
+++ gradle-4.4/debian/patches/do-not-use-classLoader-getdefinedpackages-on-java-9-50eababaa25230ab.patch	2018-10-01 20:05:23.0 +0100
@@ -0,0 +1,149 @@
+Description: Don't use ClassLoader.getDefinedPackages() on Java 9
+ Prior to this change, FilteringClassLoader invokes
+ ClassLoader.getSystemClassLoader().getParent().getDefinedPackages()
+ to get all system packages on Java 9, which is not correct.
+ ClassLoader.getDefinedPackages() only fetches packages defined by
+ the ClassLoader itself, not including its parent's. The consequence is,
+ on Java 9, most Java SE and JDK packages (e.g. java.lang) are not included in
+ FilteringClassLoader.SYSTEM_PACKAGES.
+ 
+ This PR fixes this problem by using ClassLoader.getPackages() all the time.
+Origin: upstream, https://github.com/gradle/gradle/commit/50eababaa25230abc73899eda768dd0646ddcdb4
+Bug: https://github.com/gradle/gradle/pull/5477
+Bug-Debian: https://bugs.debian.org/909905
+Forwarded: not-needed
+Applied-Upstream: 50eababaa25230abc73899eda768dd0646ddcdb4
+Last-Update: 2018-10-01
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+
+From 50eababaa25230abc73899eda768dd0646ddcdb4 Mon Sep 17 00:00:00 2001
+From: Bo Zhang 
+Date: Wed, 23 May 2018 16:24:05 +0800
+Subject: [PATCH] Don't use ClassLoader.getDefinedPackages() on Java 9 (#5477)
+

Bug#909905: gradle FTBFS when building with openjdk-11 (needs update to 4.7.0 or upstream patch)

2018-10-01 Thread Tiago Daitx
I have updated the patch to include 3 additional commits from
upstream, this fixes the build with openjdk-11 and stops gradle from
FTBFS.

The last applied patch [1], which actually gets rid of the
"NoSuchMethodError: sun.misc.Unsafe.defineClass" error, required me to
remove the kotlin classes and then put the new classes under
subprojets/base-services/ instead of subprojects/base-services-java9/
in order to get them to compile - the logic of handling the
subprojects has been moved to kotlin and I didn't check if there was a
way to get it working with separated directories under gradle's 4.4
build structure.

For now I kept the openjdk-11 version check patch as it was
originally, having the full JEP-223 might actually be a good thing - I
will let the decision to someone who understands gradle better than I
do.

Of course, always bootstrap with openjdk-10 first, after that the
generated binaries are good enough to get it to build with openjdk-11.

[1] 
debian/patches/use-lookup-instead-of-reflection-on-java-9-3db6e25698705317.patch

On Mon, Oct 1, 2018 at 8:39 PM Emmanuel Bourg  wrote:
>
> Le 01/10/2018 à 19:37, shirish शिरीष a écrit :
>
> > So are we going to have gradle 4.8 in either experimental or unstable 
> > soonish.
>
> Unfortunately no. Starting with version 4.5 Gradle requires Kotlin, and
> we are nowhere near having Kotlin in Debian. It's more likely we'll
> instead patch Gradle 4.4 and fix the Java 11 incompatibilities.
>
>
> > I'm sure you may have read the freeze time-table which was shared few days 
> > ago.
> >
> > It would be nice to have all the components in debian tested etc. well
> > before freeze.
>
> Sure but this won't happen magically, we need more contributors.
>
> Emmanuel Bourg
>


-- 
Tiago Stürmer Daitx
Software Engineer
tiago.da...@canonical.com

PGP Key: 4096R/F5B213BE (hkp://keyserver.ubuntu.com)
Fingerprint = 45D0 FE5A 8109 1E91 866E  8CA4 1931 8D5E F5B2 13BE
diff -Nru gradle-4.4/debian/changelog gradle-4.4/debian/changelog
--- gradle-4.4/debian/changelog	2018-10-01 14:12:33.0 +0100
+++ gradle-4.4/debian/changelog	2018-10-01 20:05:23.0 +0100
@@ -1,3 +1,17 @@
+gradle (4.4-4) UNRELEASED; urgency=medium
+
+  * Enable support for openjdk-11 (Closes: #909905)
+- debian/patches/enable-jdk-11-support-ac15612d41b43c39c.patch:
+  enable support for openjdk-11.
+- d/p/use-lookup-to-invoke-defineclass-java-9-028548460bd929fd.patch:
+  Use Lookup to invoke defineClass on Java 9+.
+- d/p/do-not-use-classLoader-getdefinedpackages-on-java-9-50eababaa25230ab.patch:
+  Don't use ClassLoader.getDefinedPackages() on Java 9.
+- d/p/use-lookup-instead-of-reflection-on-java-9-3db6e25698705317.path:
+  Use Lookup instead of reflection on Java 9+.
+
+ -- Tiago Stürmer Daitx   Mon, 01 Oct 2018 19:05:23 +
+
 gradle (4.4-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru gradle-4.4/debian/patches/do-not-use-classLoader-getdefinedpackages-on-java-9-50eababaa25230ab.patch gradle-4.4/debian/patches/do-not-use-classLoader-getdefinedpackages-on-java-9-50eababaa25230ab.patch
--- gradle-4.4/debian/patches/do-not-use-classLoader-getdefinedpackages-on-java-9-50eababaa25230ab.patch	1970-01-01 01:00:00.0 +0100
+++ gradle-4.4/debian/patches/do-not-use-classLoader-getdefinedpackages-on-java-9-50eababaa25230ab.patch	2018-09-29 21:25:43.0 +0100
@@ -0,0 +1,130 @@
+From 50eababaa25230abc73899eda768dd0646ddcdb4 Mon Sep 17 00:00:00 2001
+From: Bo Zhang 
+Date: Wed, 23 May 2018 16:24:05 +0800
+Subject: [PATCH] Don't use ClassLoader.getDefinedPackages() on Java 9 (#5477)
+
+Prior to this change, FilteringClassLoader invokes
+ClassLoader.getSystemClassLoader().getParent().getDefinedPackages()
+to get all system packages on Java 9, which is not correct.
+ClassLoader.getDefinedPackages() only fetches packages defined by
+the ClassLoader itself, not including its parent's. The consequence is,
+on Java 9, most Java SE and JDK packages (e.g. java.lang) are not included in
+FilteringClassLoader.SYSTEM_PACKAGES.
+
+This PR fixes this problem by using ClassLoader.getPackages() all the time.
+---
+ .../classloader/ClassLoaderUtils.java |  4 ++--
+ .../classloader/FilteringClassLoader.java | 22 +--
+ .../FilteringClassLoaderTest.groovy   |  6 +
+ .../fixtures/executer/LogContent.java |  2 +-
+ ...ConsoleJvmTestLoggingFunctionalTest.groovy |  3 ++-
+ 5 files changed, 17 insertions(+), 20 deletions(-)
+
+diff --git a/subprojects/base-services/src/main/java/org/gradle/internal/classloader/ClassLoaderUtils.java b/subprojects/base-services/src/main/java/org/gradle/internal/classloader/ClassLoaderUtils.java
+index 3995ad38be55..cdd68af5f905 100644
+--- a/subprojects/base-services/src/main/java/org/gradle/internal/classloader/ClassLoaderUtils.java
 b/subprojects/base-services/src/main/java/org/gradle/internal/classloader/ClassLoaderUtils.java
+@@ -39,7 +39,8 @@
+ 
+ static {
+ CLASS_DEFINER = 

Bug#909905: gradle FTBFS when building with openjdk-11 (needs update to 4.7.0 or upstream patch)

2018-10-01 Thread Emmanuel Bourg
Le 01/10/2018 à 19:37, shirish शिरीष a écrit :

> So are we going to have gradle 4.8 in either experimental or unstable soonish.

Unfortunately no. Starting with version 4.5 Gradle requires Kotlin, and
we are nowhere near having Kotlin in Debian. It's more likely we'll
instead patch Gradle 4.4 and fix the Java 11 incompatibilities.


> I'm sure you may have read the freeze time-table which was shared few days 
> ago.
> 
> It would be nice to have all the components in debian tested etc. well
> before freeze.

Sure but this won't happen magically, we need more contributors.

Emmanuel Bourg



Bug#909905: gradle FTBFS when building with openjdk-11 (needs update to 4.7.0 or upstream patch)

2018-10-01 Thread shirish शिरीष
at bottom :-

On 01/10/2018, Emmanuel Bourg  wrote:
> Le 01/10/2018 à 11:48, Emmanuel Bourg a écrit :
>
>> Thanks a lot for investigating this issue Tiago. I'll apply the patch.
>
> The fix for the Java version parsing issue can be reduced to:
>
> ---
> a/subprojects/base-services/src/main/java/org/gradle/api/JavaVersion.java
> +++
> b/subprojects/base-services/src/main/java/org/gradle/api/JavaVersion.java
> @@ -26,7 +26,7 @@
>  public enum JavaVersion {
>  VERSION_1_1(false), VERSION_1_2(false), VERSION_1_3(false),
> VERSION_1_4(false),
>  // starting from here versions are 1_ but their official name is "Java
> 6", "Java 7", ...
> -VERSION_1_5(true), VERSION_1_6(true), VERSION_1_7(true),
> VERSION_1_8(true), VERSION_1_9(true), VERSION_1_10(true);
> +VERSION_1_5(true), VERSION_1_6(true), VERSION_1_7(true),
> VERSION_1_8(true), VERSION_1_9(true), VERSION_1_10(true),
> VERSION_1_11(true);
>  private static JavaVersion currentJavaVersion;
>  private final boolean hasMajorVersion;
>  private final String versionName;
>
>
> But that's not enough, the build fails later due to the removal of
> sun.misc.Unsafe.defineClass in Java 11. It seems this was fixed in
> Gradle 4.8.
>

So are we going to have gradle 4.8 in either experimental or unstable soonish.

I'm sure you may have read the freeze time-table which was shared few days ago.

It would be nice to have all the components in debian tested etc. well
before freeze.

Hope to see the new releases of gradle, openjfx and rest of openjdk 11
dependencies so we have a java 11 transition if need be before hard
freeze comes up.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8



Bug#909905: gradle FTBFS when building with openjdk-11 (needs update to 4.7.0 or upstream patch)

2018-10-01 Thread Emmanuel Bourg
Le 01/10/2018 à 11:48, Emmanuel Bourg a écrit :
 
> Thanks a lot for investigating this issue Tiago. I'll apply the patch.

The fix for the Java version parsing issue can be reduced to:

--- a/subprojects/base-services/src/main/java/org/gradle/api/JavaVersion.java
+++ b/subprojects/base-services/src/main/java/org/gradle/api/JavaVersion.java
@@ -26,7 +26,7 @@
 public enum JavaVersion {
 VERSION_1_1(false), VERSION_1_2(false), VERSION_1_3(false), 
VERSION_1_4(false),
 // starting from here versions are 1_ but their official name is "Java 6", 
"Java 7", ...
-VERSION_1_5(true), VERSION_1_6(true), VERSION_1_7(true), 
VERSION_1_8(true), VERSION_1_9(true), VERSION_1_10(true);
+VERSION_1_5(true), VERSION_1_6(true), VERSION_1_7(true), 
VERSION_1_8(true), VERSION_1_9(true), VERSION_1_10(true), VERSION_1_11(true);
 private static JavaVersion currentJavaVersion;
 private final boolean hasMajorVersion;
 private final String versionName;


But that's not enough, the build fails later due to the removal of
sun.misc.Unsafe.defineClass in Java 11. It seems this was fixed in
Gradle 4.8.



Bug#909905: gradle FTBFS when building with openjdk-11 (needs update to 4.7.0 or upstream patch)

2018-10-01 Thread Emmanuel Bourg
Le 29/09/2018 à 21:41, Tiago Daitx a écrit :
> Please consider the attached patch which applies the upstream patch [1].

Thanks a lot for investigating this issue Tiago. I'll apply the patch.

Emmanuel Bourg



Bug#909905: gradle FTBFS when building with openjdk-11 (needs update to 4.7.0 or upstream patch)

2018-09-29 Thread Tiago Daitx
Please consider the attached patch which applies the upstream patch [1].

References:
[1] 
https://github.com/gradle/gradle/commit/ac15612d41b43c39c8e39d12fdd6621589b0f782
On Sat, Sep 29, 2018 at 8:33 PM Tiago Stürmer Daitx
 wrote:
>
> Package: gradle
> Version: 4.4-2
> Severity: normal
>
> Dear Maintainer,
>
> gradle 4.4-2 currently FTBFS when build with openjdk-11.
>
> * Exception is:
> java.lang.IllegalArgumentException: Could not determine java version from 
> '11'.
> at org.gradle.api.JavaVersion.toVersion(JavaVersion.java:72)
> at org.gradle.api.JavaVersion.current(JavaVersion.java:82)
> at 
> org.gradle.internal.jvm.UnsupportedJavaRuntimeException.assertUsingVersion(UnsupportedJavaRuntimeException.java:42)
> at 
> org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:32)
> at 
> org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
> at 
> org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
> at 
> org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
> at 
> org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:257)
> at 
> org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:191)
> at org.gradle.launcher.Main.doAction(Main.java:33)
> at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
> at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at 
> org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60)
> at 
> org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37)
> at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
>
> it needs either to be updated to 4.7 or have the upstream patch [1]
> applied.
>
> References:
> [1] 
> https://github.com/gradle/gradle/commit/ac15612d41b43c39c8e39d12fdd6621589b0f782#diff-1992c69962eb418e832c020dd61b2f1b.diff
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers cosmic
>   APT policy: (500, 'cosmic'), (400, 'cosmic-proposed')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.18.0-7-generic (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled



-- 
Tiago Stürmer Daitx
Software Engineer
tiago.da...@canonical.com

PGP Key: 4096R/F5B213BE (hkp://keyserver.ubuntu.com)
Fingerprint = 45D0 FE5A 8109 1E91 866E  8CA4 1931 8D5E F5B2 13BE
diff -Nru gradle-4.4/debian/changelog gradle-4.4/debian/changelog
--- gradle-4.4/debian/changelog	2018-09-17 10:15:05.0 +0100
+++ gradle-4.4/debian/changelog	2018-09-29 18:50:56.0 +0100
@@ -1,3 +1,10 @@
+gradle (4.4-3) UNRELEASED; urgency=medium
+
+  * debian/patches/enable-jdk-11-support-ac15612d41b43c39c.patch: enable
+support for openjdk-11. (Closes: #909905)
+
+ -- Tiago Stürmer Daitx   Sat, 29 Sep 2018 17:50:56 +
+
 gradle (4.4-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru gradle-4.4/debian/patches/enable-jdk-11-support-ac15612d41b43c39c.patch gradle-4.4/debian/patches/enable-jdk-11-support-ac15612d41b43c39c.patch
--- gradle-4.4/debian/patches/enable-jdk-11-support-ac15612d41b43c39c.patch	1970-01-01 01:00:00.0 +0100
+++ gradle-4.4/debian/patches/enable-jdk-11-support-ac15612d41b43c39c.patch	2018-09-29 18:50:56.0 +0100
@@ -0,0 +1,560 @@
+Description: make JavaVersion support JDK 11 and JEP-223
+ Add JavaVersion.VERSION_11 and support JEP223
+Origin: upstream, https://github.com/gradle/gradle/commit/ac15612d41b43c39c8e39d12fdd6621589b0f782
+Bug-Debian: http://bugs.debian.org/909905
+Forwarded: not-needed
+Applied-Upstream: ac15612d41b43c39c8e39d12fdd6621589b0f782
+Last-Update: 2018-09-29
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+
+From ac15612d41b43c39c8e39d12fdd6621589b0f782 Mon Sep 17 00:00:00 2001
+From: Bo Zhang 
+Date: Wed, 21 Mar 2018 16:08:44 +0800
+Subject: [PATCH] Make JavaVersion support JDK 11 and JEP-223 (#4759)
+
+Add JavaVersion.VERSION_11 and support JEP223
+---
+ .../main/java/org/gradle/api/JavaVersion.java | 123 ++
+ .../org/gradle/api/JavaVersionSpec.groovy | 212 --
+ .../changes/accepted-public-api-changes.json  |  20 ++
+ .../cli/BuildActionsFactoryTest.groovy|   8 +-
+ 4 files changed, 199 insertions(+), 164 deletions(-)
+
+--- 

Bug#909905: gradle FTBFS when building with openjdk-11 (needs update to 4.7.0 or upstream patch)

2018-09-29 Thread Tiago Stürmer Daitx
Package: gradle
Version: 4.4-2
Severity: normal

Dear Maintainer,

gradle 4.4-2 currently FTBFS when build with openjdk-11.

* Exception is:
java.lang.IllegalArgumentException: Could not determine java version from '11'.
at org.gradle.api.JavaVersion.toVersion(JavaVersion.java:72)
at org.gradle.api.JavaVersion.current(JavaVersion.java:82)
at 
org.gradle.internal.jvm.UnsupportedJavaRuntimeException.assertUsingVersion(UnsupportedJavaRuntimeException.java:42)
at 
org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:32)
at 
org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
at 
org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
at 
org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
at 
org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:257)
at 
org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:191)
at org.gradle.launcher.Main.doAction(Main.java:33)
at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at 
org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60)
at 
org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37)
at org.gradle.launcher.GradleMain.main(GradleMain.java:23)

it needs either to be updated to 4.7 or have the upstream patch [1]
applied.

References:
[1] 
https://github.com/gradle/gradle/commit/ac15612d41b43c39c8e39d12fdd6621589b0f782#diff-1992c69962eb418e832c020dd61b2f1b.diff


-- System Information:
Debian Release: buster/sid
  APT prefers cosmic
  APT policy: (500, 'cosmic'), (400, 'cosmic-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-7-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled