specifically about the version parsing we have hit some in Apache Karaf:
I previously reported the same for JDK10:
(the JDK10 related issue was resolved but it needs further changes to
deal with JDK11)
Even solving those it's a problem for OSGi testing as e.g. Pax Exam,
the integration testing tool we use to test with Karaf, was not
updated to match the latest Karaf issues. So to summarize currently
I'm not sure how to test anything on OSGi, we probably should look at
alternative integration testing tools.
Gradle is affected by the "version parsing" issue as well; it's fixed
now but wasn't released yet:
I've tested the nightly builds and it's ok, however even the nightly
builds only aim at JDK10 compatibility; JDK11 is scheduled for future
We used the nightlies to test on both JDK10 and JDK11 and it seems to
work quite well, yet I have several other failures which I believe are
not related to Gradle nor specifically to the version format, so it's
all a bit premature to evaluate.
We will of course report issues to Gradle and/or others when things get clearer.
Next, coming from our Maven projects we have Surefire also chocking on
this one was worrying me most as it took a long time to be fixed; as
you can see I reported it back in November 2017, during our JDK10
early access testing period.
Ironically some of those issues won't be triggered by the JDK11 final
release as the "-ea" part is the problem trigger, so maybe it will be
fine but it's having me disable large portions of our testsuites.
I guess the fact that JDK10 is no longer flagged as "ea" is what is
causing most of these issues to get reported in pairs: some libraries
fixed without the postfix first and then need a second patch when
people start looking at -ea versions; may I suggest to not change it
further for the LTS, or maybe even consider an enhancement: provide an
alternative to "-version" meant to facilitate machine parsing. Having
a prefix of two "--" while at it :)
I'll spare you details of the issues not related to versions at this
stage, we still have much work to do.
Thanks and regards,
On 9 May 2018 at 19:30, dalibor topic <dalibor.topic(a)oracle.com> wrote:
thank you for testing! Do you have a few URLs to share about the 11-ea
version parsing issues you've seen with other tools?
On 08.05.2018 11:14, Sanne Grinovero wrote:
> Hi Rory,
> thanks for the regular updates!
> Unfortunately many tools we need are still unable to run properly on
> JDK11 so I can't run our comprehensive tests.
> For the record, a common issue seems to be the inability to parse the
> '11-ea' version number.
> The few modules I can run "manually" in isolation didn't highlight any
> specific problem with Hibernate libraries so far, but such testing has
> been quite limited. I hope to be able to tell you more soon.
> On 8 May 2018 at 09:05, Rory O'Donnell <rory.odonnell(a)oracle.com> wrote:
>> Hi Sanne,
>> **JDK 11 EA build 12 , *****under both the GPL and Oracle EA licenses,
>> is now available at **http://jdk.java.net/11**. **
>> * Newly approved Schedule, status & features
>> o http://openjdk.java.net/projects/jdk/11/
>> * Release Notes:
>> o http://jdk.java.net/11/release-notes
>> * Summary of changes
>> *Notable changes in JDK 11 EA builds since last email:*
>> * Build 11 - see Release Notes for details.
>> o JDK-8201315 : SelectableChannel.register may be invoked while a
>> selection operation is in progress
>> * Build 10 - see Release Notes for details.
>> o JDK-8200149 : Removal of "com.sun.awt.AWTUtilities" class
>> o JDK-8189997 (not public) : Enhanced KeyStore Mechanisms
>> o JDK-8175075 (not public) : 3DES Cipher Suites Disabled
>> * Build 9: - see Release Notes for details.
>> o JDK-8200152 : KerberosString uses UTF-8 encoding by default
>> o JDK-8200458 : Readiness information previously recorded in
>> SelectionKey ready set not preserved
>> *Draft JEP: Deprecate pack200, unpack200 tools and related APIs. 
>> This draft JEP  proposes to deprecate the pack200 APIs and tools in
>> the JDK. As outlined in the JEP, the usefulness of this technology
>> have diminishing returns, the components using them are being removed
>> and connectivity speeds have improved by leaps and bounds,
>> since its inception. Feedback appreciated via
>>  http://mail.openjdk.java.net/pipermail/jdk-dev/2018-April/001074.html
>>  https://bugs.openjdk.java.net/browse/JDK-8200752
>> Rgds,Rory O'Donnell
>> Quality Engineering Manager
>> Oracle EMEA, Dublin,Ireland
>> hibernate-dev mailing list
Dalibor Topic | Principal Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg
ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
Oracle is committed to developing
practices and products that help protect the environment