[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002168#comment-17002168
]
Dennis Kieselhorst commented on CXF-8134:
-
Reverted on master and moved to
https://github.com/apache/cxf/tree/CXF-8134_CXF-8165_spring-dep-upgrade
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: image-2019-12-22-16-34-24-327.png,
> image-2019-12-22-16-34-31-499.png, image-2019-12-22-16-34-44-435.png
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002165#comment-17002165
]
Dennis Kieselhorst commented on CXF-8134:
-
Ok my bad, looks like I did the testing without properly installing the master
branch but having built the branch with the fixed dependencies before :( It's
working except the OSGi mess so I'll revert the changes and move them to a
separate branch...
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: image-2019-12-22-16-34-24-327.png,
> image-2019-12-22-16-34-31-499.png, image-2019-12-22-16-34-44-435.png
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001997#comment-17001997
]
Andriy Redko commented on CXF-8134:
---
I have just quickly picked one of our JAX-RS samples, a few examples are
immediately showing up:
* jakarta.annotation-api and javax.annotation-api
* jakarta.validation-api and validation-api
* jakarta.activation-api and javax.activation-api (not a the picture but in
dependency graph)
* ...
!image-2019-12-22-16-34-44-435.png|width=414,height=436!
There are surely more to pin point.
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: image-2019-12-22-16-34-24-327.png,
> image-2019-12-22-16-34-31-499.png, image-2019-12-22-16-34-44-435.png
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001993#comment-17001993
]
Dennis Kieselhorst commented on CXF-8134:
-
Well I share that concern but looking at our sample projects I haven't noticed
any duplicate dependencies.
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001992#comment-17001992
]
Andriy Redko commented on CXF-8134:
---
Hi [~deki] ,
I think the main concern was not regarding CXF not working with Spring Boot but
the amount of "duplicate" dependencies which are now scattered between "old"
(javax / sun / ...) and "new" (jakarta) artifacts. The CXF-7910 should have
helped us to address that. I am not sure we should have rushed with Spring Boot
2.2 upgrade before finalizing the grounding work.
Best Regards,
Andriy Redko
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957494#comment-16957494
]
Andriy Redko commented on CXF-8134:
---
Very right, thanks [~ffang], btw do you have any input on
https://issues.apache.org/jira/browse/CXF-7910, (SAAJ 1.5 vs SAAJ 1.4) it would
help us to move forward I think.
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957385#comment-16957385
]
Freeman Yue Fang commented on CXF-8134:
---
Thanks [~reta]!
We also need to upgrade to use spring framework 5.2.0 with spring boot 2.2.0
Freeman
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956494#comment-16956494
]
Andriy Redko commented on CXF-8134:
---
CC [~ffang]
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
