[jira] [Created] (MEECROWAVE-337) Migrate javax to jakarta
Shai Zambrovski created MEECROWAVE-337: -- Summary: Migrate javax to jakarta Key: MEECROWAVE-337 URL: https://issues.apache.org/jira/browse/MEECROWAVE-337 Project: Meecrowave Issue Type: Wish Reporter: Shai Zambrovski Hi 1st of all, I just want to say thanks for this great framework. There is a plan to: 1. Continue release newer versions? The last in maven repo was released on Jan 23 2. Any plan to migrate javax to jakarta namespace? It does doing some headache in our products. 3. Fix CVEs in the latest versions Thanks, Shai -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEECROWAVE-337) Migrate javax to jakarta
[ https://issues.apache.org/jira/browse/MEECROWAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821404#comment-17821404 ] Romain Manni-Bucau commented on MEECROWAVE-337: --- Hi [~shaikezam] , # I guess we upgrade transitive deps in project forcing the versions so we don't release meecrowave that often but there is no real blocker to do it # We had the jakarta bundle ([https://repo1.maven.org/maven2/org/apache/meecrowave/meecrowave-core/1.2.15/meecrowave-core-1.2.15-jakarta.jar)] which was covering it until the full stack migrates to jakarta, now openwebbeans, tomcat and cxf migrated and some years passed we can likely do it # probably check 1. which enables to be CVE free with last release feel free to do a PR to work on 2 if you are interested? > Migrate javax to jakarta > > > Key: MEECROWAVE-337 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-337 > Project: Meecrowave > Issue Type: Wish >Reporter: Shai Zambrovski >Priority: Major > > Hi > 1st of all, I just want to say thanks for this great framework. > There is a plan to: > 1. Continue release newer versions? The last in maven repo was released on > Jan 23 > 2. Any plan to migrate javax to jakarta namespace? It does doing some > headache in our products. > 3. Fix CVEs in the latest versions > Thanks, > Shai -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEECROWAVE-337) Migrate javax to jakarta
[ https://issues.apache.org/jira/browse/MEECROWAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821407#comment-17821407 ] Shai Zambrovski commented on MEECROWAVE-337: Regarding #2, if I do it, does it mean that Java8 will not be the minimum JDK-version? > Migrate javax to jakarta > > > Key: MEECROWAVE-337 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-337 > Project: Meecrowave > Issue Type: Wish >Reporter: Shai Zambrovski >Priority: Major > > Hi > 1st of all, I just want to say thanks for this great framework. > There is a plan to: > 1. Continue release newer versions? The last in maven repo was released on > Jan 23 > 2. Any plan to migrate javax to jakarta namespace? It does doing some > headache in our products. > 3. Fix CVEs in the latest versions > Thanks, > Shai -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEECROWAVE-337) Migrate javax to jakarta
[ https://issues.apache.org/jira/browse/MEECROWAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821408#comment-17821408 ] Richard Zowalla commented on MEECROWAVE-337: Played around with it yesterday as we have some Meecrowave services at university. The CXF CDI Extension in CXF 4.0.x has an issue with the latest Bean Manager Changes but can be solved with a workaround, I guess: [https://github.com/apache/cxf/blob/main/integration%2Fcdi%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fcxf%2Fcdi%2FJAXRSCdiResourceExtension.java] Can push the WIP branch to my fork, if interested. > Migrate javax to jakarta > > > Key: MEECROWAVE-337 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-337 > Project: Meecrowave > Issue Type: Wish >Reporter: Shai Zambrovski >Priority: Major > > Hi > 1st of all, I just want to say thanks for this great framework. > There is a plan to: > 1. Continue release newer versions? The last in maven repo was released on > Jan 23 > 2. Any plan to migrate javax to jakarta namespace? It does doing some > headache in our products. > 3. Fix CVEs in the latest versions > Thanks, > Shai -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEECROWAVE-337) Migrate javax to jakarta
[ https://issues.apache.org/jira/browse/MEECROWAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821434#comment-17821434 ] Mark Struberg commented on MEECROWAVE-337: -- I agree that we should move Meecrowave to native jakartaEE finally and ship a release in the near future. > Migrate javax to jakarta > > > Key: MEECROWAVE-337 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-337 > Project: Meecrowave > Issue Type: Wish >Reporter: Shai Zambrovski >Priority: Major > > Hi > 1st of all, I just want to say thanks for this great framework. > There is a plan to: > 1. Continue release newer versions? The last in maven repo was released on > Jan 23 > 2. Any plan to migrate javax to jakarta namespace? It does doing some > headache in our products. > 3. Fix CVEs in the latest versions > Thanks, > Shai -- This message was sent by Atlassian Jira (v8.20.10#820010)
