[jira] [Commented] (KARAF-5641) Karaf boot scripts need to deal with JDK10 version patterns
[
https://issues.apache.org/jira/browse/KARAF-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459595#comment-16459595
]
Sanne Grinovero commented on KARAF-5641:
Thanks a lot! Seems to work fine on JDK10, now just need a working pax-exam too
to be able to use it.
In the meantime I'm testing JDK11 now, added some comments on KARAF-5725 as
it's related to this one: the version detection pattern needs another little
tweak.
Thanks
> Karaf boot scripts need to deal with JDK10 version patterns
> ---
>
> Key: KARAF-5641
> URL: https://issues.apache.org/jira/browse/KARAF-5641
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
>Affects Versions: 4.2.0.M2
>Reporter: Sanne Grinovero
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.2.0
>
>
> The {{checkJvmVersion()}} function in the {{/bin/inc}} script of the
> distribution is not dealing with the new output of {{java -version}} of JDK10
> (and later?).
> The {{VERSION}} variable is left undefined, which then has the main
> bootscript to not set the Jigsaw modules correctly (the various JVM flags
> which need to be enabled since Java 9).
> This is a blocker to use Karaf on Java 10, which is already in candidate
> release. I don't think much else is changed compared to Java 9 so it would be
> great to sort this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KARAF-5725) Add support of JDK 11
[
https://issues.apache.org/jira/browse/KARAF-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459593#comment-16459593
]
Sanne Grinovero edited comment on KARAF-5725 at 5/1/18 10:34 AM:
-
Karaf currently fails to boot on JDK11 because JDK11 is not released yet, so
the output of {{java -version}} is:
{noformat}
openjdk version "11-ea" 2018-09-25
OpenJDK Runtime Environment 18.9 (build 11-ea+10)
OpenJDK 64-Bit Server VM 18.9 (build 11-ea+10, mixed mode)
{noformat}
The boot _bin/karaf_ script fails with:
{noformat}
/opt/apache-karaf-4.2.0/bin/inc: line 212: [: 11-ea: integer expression expected
./karaf: line 274: [: 11-ea: integer expression expected
{noformat}
Probably related to KARAF-5641
was (Author: sanne):
Karaf currently fails to boot on JDK11 because JDK11 is not released yet, so
the output of {{java -version}} is:
{noformat}
openjdk version "11-ea" 2018-09-25
OpenJDK Runtime Environment 18.9 (build 11-ea+10)
OpenJDK 64-Bit Server VM 18.9 (build 11-ea+10, mixed mode)
{noformat}
The boot _bin/karaf_ script fails with:
{noformat}
/opt/apache-karaf-4.2.0/bin/inc: line 212: [: 11-ea: integer expression expected
./karaf: line 274: [: 11-ea: integer expression expected
{noformat}
> Add support of JDK 11
> -
>
> Key: KARAF-5725
> URL: https://issues.apache.org/jira/browse/KARAF-5725
> Project: Karaf
> Issue Type: New Feature
>Affects Versions: 4.2.0
>Reporter: Lijun Liao
>Priority: Major
> Fix For: 4.2.1
>
>
> JDK 11 is the first JDK with LTS (at least 5 years) since version 9. It will
> be released in September 2018. Currently the EA for JDK 11 is available under
> http://jdk.java.net/11/. So, if possible, please consider it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5724) Add support of JDK 10
[
https://issues.apache.org/jira/browse/KARAF-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459588#comment-16459588
]
Sanne Grinovero commented on KARAF-5724:
FWIW I've tested to boot Karaf 4.2.0 using OpenJDK 10 and it seemed to boot
fine.
Used the default OpenJDK version included in Fedora 28 (which is a version 10
already!):
{code}
openjdk version "10" 2018-03-20
OpenJDK Runtime Environment (build 10+46)
OpenJDK 64-Bit Server VM (build 10+46, mixed mode)
{code}
> Add support of JDK 10
> -
>
> Key: KARAF-5724
> URL: https://issues.apache.org/jira/browse/KARAF-5724
> Project: Karaf
> Issue Type: New Feature
>Affects Versions: 4.2.0
> Environment: Java Version:
> {{$JAVA_HOME/bin/java -version}}
> {{java version "10.0.1" 2018-04-17}}
> {{Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)}}
> {{Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)}}
> OS:
> {{Ubuntu 64 Bit 16.04}}
>Reporter: Lijun Liao
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.1
>
>
> Due to the missing module corba in JDK 10 (tested with the
> serverjre-10.0.1_linux-x64), karaf cannot be started.
> Here is the error message:
> {{apache-karaf-minimal-4.2.0$ bin/karaf }}
> {{Error occurred during initialization of boot layer}}
> {{java.lang.module.FindException: Module java.corba not found}}
> Removing "java.corba" from the line "--add-modules
> java.xml.ws.annotation,java.corba,java.transaction,java.xml.bind,java.xml.ws"
> in bin/karaf fixed the above error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-5641) Karaf boot scripts need to deal with JDK10 version patterns
Sanne Grinovero created KARAF-5641:
--
Summary: Karaf boot scripts need to deal with JDK10 version
patterns
Key: KARAF-5641
URL: https://issues.apache.org/jira/browse/KARAF-5641
Project: Karaf
Issue Type: Bug
Components: karaf-boot
Affects Versions: 4.2.0.M2
Reporter: Sanne Grinovero
Fix For: 4.2.0
The {{checkJvmVersion()}} function in the {{/bin/inc}} script of the
distribution is not dealing with the new output of {{java -version}} of JDK10
(and later?).
The {{VERSION}} variable is left undefined, which then has the main bootscript
to not set the Jigsaw modules correctly (the various JVM flags which need to be
enabled since Java 9).
This is a blocker to use Karaf on Java 10, which is already in candidate
release. I don't think much else is changed compared to Java 9 so it would be
great to sort this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-3518) JDK9: endorsed directories not working any longer
[
https://issues.apache.org/jira/browse/KARAF-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379324#comment-15379324
]
Sanne Grinovero commented on KARAF-3518:
I am not a Karaf expert so can't tell for sure, but I suspect you could use the
modules system as a better replacement for the endorsed libraries. Depending on
specific needs, you might not want to replace the libraries from the JDK, but
have the platform use its own version and Karaf use the version of your choice,
having these nicely isolated. Alternatively if you need to replace the ones
from the platform, the modules system provides options for that case as well
although that's probably a less desirable way as it would impact all other
libraries running on Karaf too, while the point of the modules is to allow each
library to make its own choices.
Unfortunately I can't help developing this as I'm not familiar with the reasons
for Karaf to use endorsed libraries, but I'd be happy to test any experimental
branch or patch with our testsuite too.
> JDK9: endorsed directories not working any longer
> -
>
> Key: KARAF-3518
> URL: https://issues.apache.org/jira/browse/KARAF-3518
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core, karaf-os-integration
>Affects Versions: 4.0.0.M3
> Environment: OS X,
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b49)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b49, mixed mode)
>Reporter: Achim Nierbeck
> Labels: java9
> Fix For: 4.1.0
>
>
> following message is caught with JDK 1.9:
> {code}
> -Djava.endorsed.dirs=/Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/jre/lib/endorsed:/Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/lib/endorsed:/Users/anierbeck/Development/server/apache-karaf-4.0.0.M2/lib/endorsed
> is not supported. Endorsed standards and standalone APIs
> in modular form will be supported via the concept of upgradeable modules.
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
