[
https://issues.apache.org/jira/browse/AMQ-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703601#comment-16703601
]
Christopher L. Shannon edited comment on AMQ-7087 at 11/29/18 6:16 PM:
-----------------------------------------------------------------------
I have a commit that currently works on JDK 11 (with some caveats). You can
use JDK 11 to build and also run the broker. It also keeps compatibility with
JDK 8 so if you build with JDK 11 it will still run on JDK 8, etc. I pushed my
working commit here:
[https://github.com/cshannon/activemq/commit/68c91621a0568a0d47e66a800833e1770c27b7d8]
There are some issues however:
1) OSGI/Karaf is broken. When running tests in the karaf itest project it is
missing a bunch of dependencies. This may have something to do with the fact
that I had to upgrade the maven-bundle-plugin to work with JDK 11. We are now
using version 3.5.1. As part of the plugin update I had to comment out the
Private-Package line of the config inside the activemq-parent pom otherwise it
wouldn't include any classes in the activemq-client jar. So there's clearly
some work to be done here to get it working properly with Karaf and OSGi.
[~jbonofre] - maybe you can take a look at this if you get a chance?
2) I'm not sure about the licensing issues in terms of the new jars I had to
add. We have to include new jars now such as javax.annotation-api and jaxb-api
etc. I added the standard javax versions but I'm not sure if we can use them
because of licensing and maybe we need to find geronimo versions or other jars
that are compatible. [~dkulp] - Do you know if the licensing is an issue with
these jars?
3) There are still more dependencies we should probably update and we need to
run through the full test suite. I imagine some stuff might break when we run
all the unit tests.
was (Author: christopher.l.shannon):
I have a commit that currently works on JDK 11 (with some caveats). You can
use JDK 11 to build and also run the broker. It also keeps compatibility with
JDK 8 so if you build with JDK 11 it will still run on JDK 8, etc. I pushed my
working commit here:
[https://github.com/cshannon/activemq/commit/68c91621a0568a0d47e66a800833e1770c27b7d8]
There are some issues however:
1) OSGI/Karaf is broken. When running tests it is missing a bunch of
dependencies. This may have something to do with the fact that I had to
upgrade the maven-bundle-plugin to work with JDK 11. We are now using version
3.5.1. As part of the plugin update I had to comment out the Private-Package
line of the config inside the activemq-parent pom otherwise it wouldn't include
any classes in the activemq-client jar. So there's clearly some work to be
done here to get it working properly with Karaf and OSGi. [~jbonofre] - maybe
you can take a look at this if you get a chance?
2) I'm not sure about the licensing issues in terms of the new jars I had to
add. We have to include new jars now such as javax.annotation-api and jaxb-api
etc. I added the standard javax versions but I'm not sure if we can use them
because of licensing and maybe we need to find geronimo versions or other jars
that are compatible. [~dkulp] - Do you know if the licensing is an issue with
these jars?
3) There are still more dependencies we should probably update and we need to
run through the full test suite. I imagine some stuff might break when we run
all the unit tests.
> Add Java 11 Support
> -------------------
>
> Key: AMQ-7087
> URL: https://issues.apache.org/jira/browse/AMQ-7087
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.15.6
> Environment: Windows 10 with the OpenJDK 11 "bin" directory on the
> path.
> Reporter: Jeff Gullett
> Assignee: Christopher L. Shannon
> Priority: Critical
> Fix For: 5.16.0
>
>
> Java 8 support is ending in January, 2019 (in 2 months). Currently, the
> ActiveMQ Broker only supports Java 8. When I try to start the broker using
> Java 11 (the latest long-term-support version), I get the following error:
> Unable to execute Java command. The system cannot find the file specified.
> (0x2)
> Critical error: wait for JVM process failed
> Since both Java 9 and Java 10 are already EOL, support for Java 11 needs to
> be added by January 2019. The issue to add Java 9 support (AMQ-6864) is OBE,
> and should be replaced by this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
