[ 
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)

Reply via email to