[ 
https://issues.apache.org/jira/browse/AMQ-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703404#comment-16703404
 ] 

Jezza edited comment on AMQ-7087 at 11/29/18 4:05 PM:
------------------------------------------------------

To make matters even more annoying, the broker and the client use the same 
packages, so I can't even get it to my project to compile.
Not complaining, just saying that the packages will also need to be taken into 
account.


Packages:

broker:

{noformat}
org.apache.activemq
org.apache.activemq.advisory
org.apache.activemq.broker
org.apache.activemq.filter
org.apache.activemq.memory
org.apache.activemq.network
org.apache.activemq.plugin
org.apache.activemq.proxy
org.apache.activemq.security
org.apache.activemq.store
org.apache.activemq.transaction
org.apache.activemq.transport
org.apache.activemq.usage
org.apache.activemq.util
{noformat}

client:

{noformat}
org.apache.activemq
org.apache.activemq.advisory
org.apache.activemq.blob
org.apache.activemq.broker
org.apache.activemq.command
org.apache.activemq.filter
org.apache.activemq.jndi
org.apache.activemq.management
org.apache.activemq.openwire
org.apache.activemq.selector
org.apache.activemq.state
org.apache.activemq.thread
org.apache.activemq.transaction
org.apache.activemq.transport
org.apache.activemq.usage
org.apache.activemq.util
org.apache.activemq.wireformat
{noformat}

They both declare classes in those packages.
The only exception is the "org.apache.activemq" package as only the client 
declares classes there.

Side-note: We only use the broker project, so I can't say much else about the 
others.



was (Author: jezza):
To make matters even more annoying, the broker and the client use the same 
packages, so I can't even get it to my project to compile.
Not complaining, just saying that the packages will also need to be taken into 
account.

> 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)

Reply via email to