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

Alexandre Fruchaud edited comment on AMQ-8026 at 10/3/20, 8:28 AM:
-------------------------------------------------------------------

I can provide some help with this issue.

First the official spring [migration 
guide|[https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-5.x]]

This would mean upgrading java version to the required version by spring, which 
is 1.8. Since java 11 is the [latest LTS 
version|[https://www.oracle.com/java/technologies/java-se-support-roadmap.html]],
 I'm wondering if ugrade of jdk version should be 1.7 => 1.8 => 11 or 1.7 => 11 
directly (that may cause problem with the module system of jdk 9 however).

I guess another issue should be open and resolved for jdk migration if it 
doesn't already exist.

 

 


was (Author: mmacphail):
I can provide some help with this issue.

First the official spring [migration 
guide|[https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-5.x].]

This would mean upgrading java version to the required version by spring, which 
is 1.8. Since java 11 is the [latest LTS 
version|[https://www.oracle.com/java/technologies/java-se-support-roadmap.html]],
 I'm wondering if ugrade of jdk version should be 1.7 => 1.8 => 11 or 1.7 => 11 
directly (that may cause problem with the module system of jdk 9 however).

I guess another issue should be open and resolved for jdk migration if it 
doesn't already exist.

 

 

> Upgrade to Spring 5.x
> ---------------------
>
>                 Key: AMQ-8026
>                 URL: https://issues.apache.org/jira/browse/AMQ-8026
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 5.17.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to