[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta

[Jira]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765831#comment-17765831
 ] 

Thomas Frühbeck commented on DELTASPIKE-1434:
-

I really care about OSS and would like to continue using deltaspike!

I tried a spike to continue the existing work on migration to jakarta namespace 
and it works for me on Wildfly 29.0.1.Final. Unfortunately I have neither 
experience  nor use for other containers.

As I see the variants of EE and CDI containers is enormous and mostly outdated. 
Additionally file like the META-INF/services definitions would have to be 
renamed. Wouldnt it make sense to remove old CDI support?

Anycase I would try to assist in lifting Deltaspike to jakarta if needed.

> 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

[Krzysztof Wolny (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722247#comment-17722247
 ] 

Krzysztof Wolny commented on DELTASPIKE-1434:
-

FYI: We migrated from DeltaSpike and replaced it with Weld (already been there 
partially). We also dropped the usage of {{{}CDIUnit{}}}, which also is not 
migrated jet, and replaced it with {{{}weld-testing{}}}. 

> 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

[Romain Manni-Bucau (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715964#comment-17715964
 ] 

Romain Manni-Bucau commented on DELTASPIKE-1434:


[~vanta] EE always had been selected for its stability until they start 
breaking and the adoption decrease so yes they exist and try to migrate without 
having to do it every year cause it costs money.

To answer your timeline question: it is not about the timeline since ASF does 
not have any strong timeline, it is likely more about the investment you can do.

For example join the discussion about the pruning on the list and when there is 
an agreement, if you cover all mainstream servers (I guess payara, tomee, 
wildfly) for the IT then the release is 3 days (vote process) but has no real 
blocker nor challenge.

If you consider the project as a consommable and don't care about the OSS side 
I'm tempted to say you should migrate to something more commercial like quarkus 
(money helps to maintain software in real life ;)).

> 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

[Krzysztof Wolny (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715959#comment-17715959
 ] 

Krzysztof Wolny commented on DELTASPIKE-1434:
-

> 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.

If the EE world is changing, its users have to adopt or leave if it's too fast 
for them. It's not DS fault that these changes happen, no one will blame you. 
People will blame if these changes are not adopted in DS. Why do we (waiting 
users) have to wait for these slower ones maybe they don't even exist...?

Anyway, do we have a timeline for this change or a timeline for a timeline for 
this change? All we need is clarity: should we wait or migrate to other 
solutions.

> 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

[Romain Manni-Bucau (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta

[Jeremy Landis (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715791#comment-17715791
 ] 

Jeremy Landis commented on DELTASPIKE-1434:
---

Classifier was there but deltaspike broke it.  1.9.7 release would have 
resolved that but now it's much more...

Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android


> 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

[Martin Tzvetanov Grigorov (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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

[Martin Tzvetanov Grigorov (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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

[Romain Manni-Bucau (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715768#comment-17715768
 ] 

Romain Manni-Bucau commented on DELTASPIKE-1434:


[~mgrigorov] this can look accurate but in pactise you hide the most important 
points:
 * 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 (if you 
don't it means you will do a pure conversion release then break with next 
major, likely worse),
 * javax -> jakarta is not only about renaming, EE broke itself just after the 
renaming (CDI API for ex) so this is not only a renaming thing to migrate, this 
is also why the bytecode manipulation often works but also fails regularly,
 * even following this rule you still hit the fact containers are not up to 
date or no more compatible so you still have IT work

> 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

[Martin Tzvetanov Grigorov (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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

[Romain Manni-Bucau (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715725#comment-17715725
 ] 

Romain Manni-Bucau commented on DELTASPIKE-1434:


The main issue is migrating away from it means doing yourself part of it since 
there is no real alternative in CDI land (microprofile is insanely unstable and 
doesnt cover 60% of DS) so tempted to say it depends what you use. For your 
information there are discussions on what should be kept for v2 (jakarta) or 
not on the list. As usual it is easy to say to the OSS "do my job" but the idea 
is more "join and help" so you are both welcome to join the list and do PR to 
make it move faster.

> 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

[Thomas Andraschko (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715722#comment-17715722
 ] 

Thomas Andraschko commented on DELTASPIKE-1434:
---

100% of the still active commiters maintains multiple Java/JakartaEE projects 
on apache here, DeltaSpike is just that with the lowest prio for us.
We first try to get all other libs running again, so we have "our" application 
server (TomEE) before we can even use DeltaSpike again. Its not an easy task to 
migrate like 15 libs from javax to jakarta.

We need at least some tests running on real containers, everyone can help here 
migrating the tests.





> 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

[Krzysztof Wolny (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715695#comment-17715695
 ] 

Krzysztof Wolny commented on DELTASPIKE-1434:
-

+1 for [~romanmueller] , it's a bit of shame that after 2 years it's still not 
migrated to Jakarta. Maybe this project is simply dying and we should migrate 
out of it.

> 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

[Jira]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715601#comment-17715601
 ] 

Roman Müller commented on DELTASPIKE-1434:
--

Consider migrating away from Deltaspike. It is not that much value it adds to 
your project anyway tbh. We did it for our project and it only took 2 weeks. 
Way faster than making Deltaspike compatible with Jakarta.

> 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

[Romain Manni-Bucau (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715306#comment-17715306
 ] 

Romain Manni-Bucau commented on DELTASPIKE-1434:


The harm would be to just deliver soemthing broken and imply people keep 
investing time in pure lost, we dont work like that. As of today arquillian is 
partially ready so question is the container coverage we want. I guess payara, 
tomee, maybe wildfly (less sure today). Feel free to help to uodate the setup 
Jeremy to make it move faster.

> 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

[Jeremy Landis (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715179#comment-17715179
 ] 

Jeremy Landis commented on DELTASPIKE-1434:
---

Can we just old school this and release 2.0 milestone?  Total blocker 
otherwise.  I mean what's the harm in doing so?  Those of us that keep asking 
are willing to real world test it.

Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android


> 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

[Thomas Andraschko (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714994#comment-17714994
 ] 

Thomas Andraschko commented on DELTASPIKE-1434:
---

our integrationtests are built to run on different javax containers in 1.x
noone tried to migrate those to jakarta containers yet, even not sure if 
arquillian is ready etc.

> 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

[Krzysztof Wolny (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714982#comment-17714982
 ] 

Krzysztof Wolny commented on DELTASPIKE-1434:
-

Not sure if I got your second sentence. Do you say you don't have enough 
automated integration tests and you need help to test it manually somehow?

> 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

[Thomas Andraschko (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714964#comment-17714964
 ] 

Thomas Andraschko commented on DELTASPIKE-1434:
---

i migrated most of the modules to jakarta last month but we still dont have 
running integration tests
if you have time to get all tests running on recent containers, i can help on 
fixing the tests.

> 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

[Krzysztof Wolny (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714921#comment-17714921
 ] 

Krzysztof Wolny commented on DELTASPIKE-1434:
-

Any update on the timeline? It's a blocker for us. This change started in 2021, 
it's 2023 and it's not finished :( 

> 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

[Jeremy Landis (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681506#comment-17681506
 ] 

Jeremy Landis commented on DELTASPIKE-1434:
---

Adding to that.  You have to exclude all the main artifacts and use just the 
jakarta classifiers.  1.9.6 was too aggressive on the package updates.  Master 
is fine.  Assume others may just be stuck on that part.  Personally to make 
progress need what is working released even if other issues.

Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android


> 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

[Jeremy Landis (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681504#comment-17681504
 ] 

Jeremy Landis commented on DELTASPIKE-1434:
---

Can you release master as is?  It's already jakarta.  1.9.6 is broken for 
jakarta.  It's been fixed on master for a long time now.  Think the community 
just wants it released as it is so its usable.  It's a complete broker and 
requires little effort...please 1.9.7...

Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android


> 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

[Mark Struberg (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681449#comment-17681449
 ] 

Mark Struberg commented on DELTASPIKE-1434:
---

Romain is correct. Right now I'm investigating this. Eclipse Jakarta rules 
actually forbid such changes. Some of them nonetheless sneaked into the CDI-4.0 
specification. Otoh there are a few APIs which were deprecated in older CDI 
versions already and now got pruned. Those changes are fine and we need to 
update our code

To your last question [~mcollovati] : yes, we plan to do a Jakarta10 version. 
Think this is really worth it to be the target for our next major release.

Btw this has nothing to do with OpenWebBeans. OWB-4.0.x is CDI-4.0 as well.

> 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

[Romain Manni-Bucau (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17678135#comment-17678135
 ] 

Romain Manni-Bucau commented on DELTASPIKE-1434:


CDI 4.0 is not backward compatible with CDI 3.0 (both in jakarta namespace), it 
requires some codechange to ensure it can run on both but can also mean we drop 
CDI 1.0 support (supporting 1, 2 and 4 is way harder than 2-4). Surely 
something to discuss on the list.

> 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

[Marco Collovati (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17678130#comment-17678130
 ] 

Marco Collovati commented on DELTASPIKE-1434:
-

Hi, we tried to use the shadow jakarta version of DeltaSpike 1.9.7-SNAPSHOT, 
but it seems it is not compatible with Jakarta 10 and CDI 4.0 (perhaps because 
of  OpenWebBeans).

Are there any plans to upgrade to Jakarta 10?

> 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

[Jeremy Landis (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643606#comment-17643606
 ] 

Jeremy Landis commented on DELTASPIKE-1434:
---

Most likely this issue has been fixed for some time on the master build, we 
would like a release please as the original jakarta in this repo is entirely 
unusable due to over aggressively changing javax to jakarta where not 
appropriate.

> 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

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564621#comment-17564621
 ] 

ASF subversion and git services commented on DELTASPIKE-1434:
-

Commit d090c528ea6020bdadcdf6a1380bda049b595bde in deltaspike's branch 
refs/heads/master from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=d090c528 ]

DELTASPIKE-1434 - Adds relocation pattern for javax.el, javax.servlet, 
javax.decorator, javax.faces


> 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 10m
>  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

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544742#comment-17544742
 ] 

ASF subversion and git services commented on DELTASPIKE-1434:
-

Commit 236dce676af78eb6f8680be71ebdff6b4a84d844 in deltaspike's branch 
refs/heads/master from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=236dce67 ]

DELTASPIKE-1434 - Adds relocation pattern for javax.persistence


> 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: 1h
>  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.7#820007)

[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536844#comment-17536844
 ] 

ASF subversion and git services commented on DELTASPIKE-1434:
-

Commit 4d73324914630f03f03c030738d44a0438818943 in deltaspike's branch 
refs/heads/master from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=4d733249 ]

DELTASPIKE-1434 - Refine relocation patterns for javax -> jakarta + adds 
service transformer

Signed-off-by: Mark Struberg 


> 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: 20m
>  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.7#820007)

[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta

[Jira]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443681#comment-17443681
 ] 

Roman Müller commented on DELTASPIKE-1434:
--

Hello, when depending on Deltaspike Data with jakarta classifier.

 
{quote}        
            org.apache.deltaspike.modules
            deltaspike-data-module-api
            1.9.6-SNAPSHOT
            compile
            jakarta
        
        
            org.apache.deltaspike.modules
            deltaspike-data-module-impl
            1.9.6-SNAPSHOT
            runtime
            jakarta
        
        
            jakarta.platform
            jakarta.jakartaee-api
            9.1.0
            provided
        
{quote}
 

My project fails to compile this class

 
{quote}
package de.pharmacontrol.core.archive;

import org.apache.deltaspike.data.api.EntityManagerResolver;
import jakarta.ejb.Stateless;
import jakarta.persistence.PersistenceContext;
import jakarta.persistence.EntityManager;

public class ArchiveEntityManagerResolver implements EntityManagerResolver {
    
    @PersistenceContext(unitName = "ars")
    private EntityManager archiveEm;

    public EntityManager resolveEntityManager() {
        return archiveEm;
    }
}
{quote}
With error

 
{quote}[ERROR] 
C:\Users\mueller-83\Development\Workspace\psm\psa\psm\src\main\java\de\pharmacontrol\core\archive\ArchiveEntityManagerResolver.java:[9,7]
 error: cannot access EntityManager
[ERROR]   class file for javax.persistence.EntityManager not found
[ERROR] 
C:\Users\mueller-83\Development\Workspace\psm\psa\psm\src\main\java\de\pharmacontrol\core\archive\ArchiveEntityManagerResolver.java:[14,25]
 error: resolveEntityManager() in ArchiveEntityManagerResolver cannot implement 
resolveEntityManager() in EntityManagerResolver
[ERROR] -> [Help 1]
{quote}
I use custom EntityManagerResolver implementation to provide alternative 
EntityManager in some Deltaspike repositories.

> 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
>
> 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.1#820001)

[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta

[Alex Roytman (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407627#comment-17407627
 ] 

Alex Roytman commented on DELTASPIKE-1434:
--

deltaspike-core-impl jakarta artifacts embeds api artifact and references non 
jakarta artifact in its pom

excluding api artifact resolves the issue of duplicate beans however exception 
is still thrown

 
{noformat}
Exception in thread "main" org.jboss.weld.exceptions.DeploymentException: 
Exception List with 6 exceptions:Exception in thread "main" 
org.jboss.weld.exceptions.DeploymentException: Exception List with 6 
exceptions:Exception 0 :org.jboss.weld.exceptions.DeploymentException: 
WELD-001408: Unsatisfied dependencies for type DeltaSpikeContextExtension with 
qualifiers @Default  at injection point [BackedAnnotatedField] @Inject private 
org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.deltaSpikeContextExtension
  at 
org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.deltaSpikeContextExtension(WindowContextProducer.java:0)
 at 
org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:378)
 at 
org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:290) 
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:143) 
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:164) at 
org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:526) at 
org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:64)
 at 
org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:62)
 at 
org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62){noformat}
  

> 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
>
> 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] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta

[Alex Roytman (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407024#comment-17407024
 ] 

Alex Roytman commented on DELTASPIKE-1434:
--

when including 
{noformat}

 org.apache.deltaspike.core
 deltaspike-core-impl
 ${deltaspike.version}
 jakarta
 runtime
 {noformat}
 

I have not had chance to exclude dependencies of shaded impl and include them 
explicitly with jakarta classifier. will try tomorrow but meanwhile wanted to 
share it with you 

 

lots of warnings

 

 
{noformat}
WARN: WELD-ENV-002008: Bean class 
org.apache.deltaspike.core.api.config.ConfigResolver$ConfigHelper found in 
multiple bean archives - this may result in incorrect behavior: 
 - WeldBeanDeploymentArchive 
[id=/C:/Users/roytmana/.m2/repository/org/apache/deltaspike/core/deltaspike-core-api/1.9.6-SNAPSHOT/deltaspike-core-api-1.9.6-20210827.210308-1.jar],
 - WeldBeanDeploymentArchive 
[id=/C:/Users/roytmana/.m2/repository/org/apache/deltaspike/core/deltaspike-core-impl/1.9.6-SNAPSHOT/deltaspike-core-impl-1.9.6-20210827.210342-1-jakarta.jar]
Aug 30, 2021 10:12:40 PM org.jboss.weld.environment.se.Weld createDeployment
 
{noformat}
 

and then failure

 
{noformat}
org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied 
dependencies for type DeltaSpikeContextExtension with qualifiers 
@Defaultorg.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied 
dependencies for type DeltaSpikeContextExtension with qualifiers @Default  at 
injection point [BackedAnnotatedField] @Inject private 
org.apache.deltaspike.core.impl.scope.viewaccess.ViewAccessContextArtifactProducer.deltaSpikeContextExtension
  at 
org.apache.deltaspike.core.impl.scope.viewaccess.ViewAccessContextArtifactProducer.deltaSpikeContextExtension(ViewAccessContextArtifactProducer.java:0)
 at 
org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:378)
 at 
org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:290) 
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:143) 
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:164) at 
org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:526) at 
org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:64)
 at 
org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:62)
 at 
org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
 at 
org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
 at 
org.jboss.weld.executor.CommonForkJoinPoolExecutorServices.lambda$wrap$0(CommonForkJoinPoolExecutorServices.java:70)
 at 
java.base/java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(ForkJoinTask.java:1448)
 at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) 
at 
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
 at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656) at 
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594) 
at 
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:177)Exception
 1 :org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied 
dependencies for type DeltaSpikeContextExtension with qualifiers @Default  at 
injection point [BackedAnnotatedField] @Inject private 
org.apache.deltaspike.core.impl.scope.conversation.GroupedConversationArtifactProducer.deltaSpikeContextExtension
  at 
org.apache.deltaspike.core.impl.scope.conversation.GroupedConversationArtifactProducer.deltaSpikeContextExtension(GroupedConversationArtifactProducer.java:0)
 at 
org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:378)
 at 
org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:290) 
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:143) 
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:164) at 
org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:526) at 
org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:64)
 at 
org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:62)
 at 
org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
 at 
org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
 at 
org.jboss.weld.executor.CommonForkJoinPoolExecutorServices.lambda$wrap$0(CommonForkJoinPoolExecutorServices.java:70)
 at 
java.base/java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(ForkJoinTask.java:1448)
 at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) 
at 
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
 at 

[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta

[Mark Struberg (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406662#comment-17406662
 ] 

Mark Struberg commented on DELTASPIKE-1434:
---

Hi [~roytmana] It's deployed to the ASF repository 
https://repository.apache.org/content/groups/snapshots/
e.g. 
https://repository.apache.org/content/groups/snapshots/org/apache/deltaspike/core/deltaspike-core-impl/1.9.6-SNAPSHOT/

> 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
>
> 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] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta

[Alex Roytman (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406523#comment-17406523
 ] 

Alex Roytman commented on DELTASPIKE-1434:
--

Hello Mark,

 

Is it available in maven central or I need to pull it in apache repo? If so 
could you share URL please

> 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
>
> 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] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta

[Mark Struberg (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406031#comment-17406031
 ] 

Mark Struberg commented on DELTASPIKE-1434:
---

Hi [~mgrigorov] and [~roytmana], I've just added shading for additional 
attached artifacts with qualifier 'jakarta'. Could you please give it a try and 
report back? Txs a lot!

> 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
>
> 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] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406030#comment-17406030
 ] 

ASF subversion and git services commented on DELTASPIKE-1434:
-

Commit 003b3593ee3ad4cf8aa8d3538fe92f71fb12670c in deltaspike's branch 
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=003b359 ]

DELTASPIKE-1434 add shading for jakarta EE package names

This commit adds shading from javax to jakarta namespace
as aditional attachted artifacts with qualifier 'jakarta'.


> 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
>
> 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] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta

[Alex Roytman (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17400575#comment-17400575
 ] 

Alex Roytman commented on DELTASPIKE-1434:
--

Hello [~struberg]

Any update on using deltaspike with Jakarta EE?

Any dates for availability by any chance?

> 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] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta

[Martin Tzvetanov Grigorov (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta

[Mark Struberg (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17373247#comment-17373247
 ] 

Mark Struberg commented on DELTASPIKE-1434:
---

We will create a shaded version of DeltaSpike with a quallifier. Supporting 
both specs that way.
Happy for a PR if you want to give it a try?

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