[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=17827810#comment-17827810 ] Romain Manni-Bucau commented on MEECROWAVE-337: --- [~arne] cxf just released 4.0.4, if it does not work we should clearly request them to fix it since there are solution for the dropped API. +1 to not fork now > 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=17827803#comment-17827803 ] Arne Limburg commented on MEECROWAVE-337: - I started working on it: [https://github.com/ArneLimburg/openwebbeans-meecrowave] If someone wants to step in, I can push it in a branch in the main repo. The cxf integration is not as easy as expected. Does someone know how far away the first release of cxf 4.1 is? Maybe we should wait for it since it targets CDI 4.0. Otherwise we have to copy most of the stuff to migrate it to CDI 4.0. Wdyt? > 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=17822296#comment-17822296 ] Romain Manni-Bucau commented on MEECROWAVE-337: --- Sure, while needed no issue but no reordering for ex. Idea is in the diff only required changes when possible...after we are not PR extremists ;). > 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=17822290#comment-17822290 ] Shai Zambrovski commented on MEECROWAVE-337: [~romain.manni-bucau] , migrate from javax to jakarta is kinda full style refactoring > 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=17822255#comment-17822255 ] Romain Manni-Bucau commented on MEECROWAVE-337: --- [~shaikezam] we move to the min of cxf/owb for java version, yes. No strong guidelines, idea is to limit the changes to the minimum, avoid wildcard imports or full style refactoring and ensure tests still pass and add tests if you add something new. Nothing crazy normally. > 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=17822236#comment-17822236 ] Shai Zambrovski commented on MEECROWAVE-337: [~romain.manni-bucau] Regarding #2: # if I do it, does it mean that Java8 will not be the minimum JDK-version? # there is any how to for best practices, do & don't do regarding contribute to meecrowave project? > 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=17822158#comment-17822158 ] Romain Manni-Bucau commented on MEECROWAVE-337: --- [~rzo1] this is the kind of thing I was thinking about, we can just override `public void injectBus` and restore an override of the extension (just needs to register an openwebbeans loaderservice filtering cxf extension and replacing it by ours which is disabled if cxf is not in the cp, nothing crazy IMHO if there is some will to do it early). > 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=17822142#comment-17822142 ] Richard Zowalla commented on MEECROWAVE-337: [~romain.manni-bucau] JAXRSCdiResourceExtension ** uses removed API from BeanManager (fireEvent(...)) + [https://github.com/apache/cxf/blob/main/integration/cdi/src/main/java/org/apache/cxf/cdi/JAXRSCdiResourceExtension.java#L271] (which needs to be an InectionTargetFactory now - I guess - inside of CdiBusBean). So basically we would need to rework the cdi integration of cxf (or get it from the CXF 4.1.0-SNAPSHOT branch) > 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=17822140#comment-17822140 ] Romain Manni-Bucau commented on MEECROWAVE-337: --- [~rzo1] which issue ? We worked around multiple times cxf limitations so can be done yet another time depending what it is. > 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=17822109#comment-17822109 ] Richard Zowalla commented on MEECROWAVE-337: Think this is currently blocked by [JAXRSCdiResourceExtension.java|https://github.com/apache/cxf/blob/main/integration%2Fcdi%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fcxf%2Fcdi%2FJAXRSCdiResourceExtension.java] from CXF. They fixed it in 4.1.0-SNAPSHOT for cdi4, but that artifact is not available ;) - so if we want to go for owb4 directly here, we might need to wait for the CXF people (or build a workaround). Reto told me, that they might move on with 4.1.0 sooner or later. > 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=17821610#comment-17821610 ] Arne Limburg commented on MEECROWAVE-337: - I am stepping in, because I am interested in that, too. Anything where I can help? > 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=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)
[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=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=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=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)
