[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715790#comment-17715790 ] Martin Tzvetanov Grigorov commented on DELTASPIKE-1434: --- By the way, I also got rid of DeltaSpike, so I am no more interested in the Jakarta change. I will unsubscribe myself from this ticket. > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Assignee: Mark Struberg >Priority: Major > Time Spent: 2h 50m > Remaining Estimate: 0h > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715784#comment-17715784 ] Martin Tzvetanov Grigorov commented on DELTASPIKE-1434: --- "this is a breaking version so you have to ask yourself as a project maintainer what you want to break more to give some stability to users" Releases are cheap! There is no rule saying that a project can't make several major releases in a (short) period. IMO it would be better to make a release that just replaces "javax" with "jakarta" of the current/latest javax version of a lib. There is no need of a major version here. One could use even a Maven classifier. And then take your time to make any improvements on top for the next major release. What we have now is 2 years of waiting... And probably more ahead ... > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Assignee: Mark Struberg >Priority: Major > Time Spent: 2h 50m > Remaining Estimate: 0h > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715729#comment-17715729 ] Martin Tzvetanov Grigorov commented on DELTASPIKE-1434: --- "there are discussions on what should be kept for v2 (jakarta) or not on the list." This is the main problem for all Javax/Jakarta projects - they all try to add/remove something in addition to the simple renaming of the packages/imports. And this makes this simple task so problematic. I see the same problem in commons-fileupload, in RestEasy, in cdi-unit and few more projects. Most of us (the users) just want the same old javax-based library but updated to jakarta. Some projects update the sources, others use bytecode manipulation to accomplish the task. Both are fine for us (the users)! What should be avoided is to add/remove features in the same release. > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Assignee: Mark Struberg >Priority: Major > Time Spent: 2h 50m > Remaining Estimate: 0h > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17381884#comment-17381884 ] Martin Tzvetanov Grigorov commented on DELTASPIKE-1434: --- JBoss people use [https://github.com/wildfly-extras/batavia] for this. The README/howto is not very helpful though. > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Priority: Major > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DELTASPIKE-1430) Migrate to Jakarta EE
Martin Tzvetanov Grigorov created DELTASPIKE-1430: - Summary: Migrate to Jakarta EE Key: DELTASPIKE-1430 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1430 Project: DeltaSpike Issue Type: Task Security Level: public (Regular issues) Reporter: Martin Tzvetanov Grigorov Please provide version of DeltaSpike that depends on Jakarta EE APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
