[
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715794#comment-17715794
]
Romain Manni-Bucau commented on DELTASPIKE-1434:
------------------------------------------------
> Releases are cheap! There is no rule saying that a project can't make several
> major releases in a (short) period.
Not for end users when they need to change their code every year/month (maybe
you are an exception), the EE and Microprofile mess prove it being very true
for a lot of our user base.
> And then take your time to make any improvements on top for the next major
> release.
Deleting will not happen *on top*, this is the main issue and why there is a
discussion.
> 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.
I was for the classifier option to have an early access flavor but the breaking
change in EE API limit this solution now and will not enable to run in any
jakarta server so we have to do the big jump sadly and therefore the IT
question which require some investment.
> 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)
