[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&focusedCommentId=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

[Jeremy Landis (Jira)]

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

[Jeremy Landis (Jira)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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&focusedCommentId=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] [Created] (DELTASPIKE-1459) Please release master so jakarta namespace will work

[Jeremy Landis (Jira)]

Jeremy Landis created DELTASPIKE-1459:
-

 Summary: Please release master so jakarta namespace will work
 Key: DELTASPIKE-1459
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1459
 Project: DeltaSpike
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Build
Affects Versions: 1.9.6
Reporter: Jeremy Landis


The released jakarta was overly aggressive changing javax to jakarta that do 
not exist.  This was fixed on master.  The repo has no zero activity since 
July.  Please release this.  Its impossible to use this with jakarta right now 
which is a high blocker.

 

Would also be nice to use some 'bom's - one for legacy and one for jakarta.  
The method used to make this jakarta is a mad mess.  We have to add exclusions 
to nearly everything to get non jakarta components to go away.  This is a 
separate issue but worth pointing out just how incredibly difficult this is to 
use.



--
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&focusedCommentId=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-1458) DefaultConfigSourceProvider cannot be instantiated

[Jeremy Landis (Jira)]

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

Jeremy Landis commented on DELTASPIKE-1458:
---

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.

> DefaultConfigSourceProvider cannot be instantiated
> --
>
> Key: DELTASPIKE-1458
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1458
> Project: DeltaSpike
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: Michael Heydemann
>Priority: Major
>
> Hello,
> I am trying to use the deltaspike test module (CdiTestRunner) in a Jakarta 
> environment. Therefore for some of the dependencies I added the jakarta 
> classifier. The test then fails with an exception. For demonstration purose I 
> reduced the project to the necessary:
> I get this stack trace during test execution:
> {code:java}
> java.util.ServiceConfigurationError: 
> org.apache.deltaspike.core.spi.config.ConfigSourceProvider: Provider 
> org.apache.deltaspike.core.impl.config.DefaultConfigSourceProvider could not 
> be instantiated
> at java.util.ServiceLoader.fail(ServiceLoader.java:232)
> at java.util.ServiceLoader.access$100(ServiceLoader.java:185)
> at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:384)
> at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)
> at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
> at 
> org.apache.deltaspike.core.util.ServiceUtils.loadServiceImplementations(ServiceUtils.java:81)
> at org.apache.deltaspike.core.impl.config.ConfigImpl.init(ConfigImpl.java:80)
> at 
> org.apache.deltaspike.core.impl.config.ConfigProviderImpl.getConfig(ConfigProviderImpl.java:53)
> at 
> org.apache.deltaspike.core.impl.config.ConfigProviderImpl.getConfig(ConfigProviderImpl.java:43)
> at 
> org.apache.deltaspike.core.api.config.ConfigResolver.resolve(ConfigResolver.java:655)
> at 
> org.apache.deltaspike.testcontrol.api.junit.TestBaseConfig$ContainerIntegration.(TestBaseConfig.java:29)
> at 
> org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner.(CdiTestRunner.java:89)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> Caused by: java.lang.NoClassDefFoundError: jakarta/naming/NamingException
> at 
> org.apache.deltaspike.core.impl.config.LocalJndiConfigSource.getPropertyValue(LocalJndiConfigSource.java:53)
> at 
> org.apache.deltaspike.core.impl.config.BaseConfigSource.initOrdinal(BaseConfigSource.java:54)
> at 
> org.apache.deltaspike.core.impl.config.LocalJndiConfigSource.(LocalJndiConfigSource.java:39)
> at 
> org.apache.deltaspike.core.impl.config.DefaultConfigSourceProvider.(DefaultConfigSourceProvider.java:59)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:380)
> ... 26 more
> Caused by: java.lang.ClassNotFoundException: jakarta.naming.NamingException
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 36 more{code}
>  
> Here the pom.xml:
> {code:java}
>xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd";
>   xmlns="http://maven.apache.org/POM/4.0.0";
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>   4.0.0
>   org.example.cdi.test
>   cdi-test
>   1.0.0-SNAPSHOT
>   jar
>   
> 1.9.6
>   
>   
> 
>   org.apache.deltaspike.modules
>   deltaspike-test-control-module-api
>   ${deltaspike.version}
>   jakarta
>   test
> 
> 
>   org.apache.deltaspike.modules
>   deltaspike-test-control-module-impl
>   ${deltaspike.version}
>   jakarta
>   test
> 
> 
>   org.apache.deltaspike.cdictrl
>   deltaspike-cdictrl-weld
>   ${deltaspike.version}
>   jakarta
>   test
> 
> 
>   org.jboss.weld.se
>   weld-se-core
>   4.0.0.Alpha3
>   test
> 
> 
>   junit
>   junit
>   4.12
>   test
> 
>   
> 
> {code}
>  
> And the empty test I would like to execute:
> {code:java}
> import org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner;
> import org.junit.Test;
> import org.junit.runner.RunWith;
> @RunWith(CdiTestRunner.class)
> public class CdiTest {
>   @Test
>   public void test() {}
> }
> {code}
>  
> I hope you can help me with this.
> Best Regrads,
> Michael



--
This message was sent by Atlassia

[jira] [Commented] (DELTASPIKE-1448) Deltaspike fails with weld 3.1.7+

[Jeremy Landis (Jira)]

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

Jeremy Landis commented on DELTASPIKE-1448:
---

Yes original concern is now addressed.  There is still a problem with Weld 
proxy changes running deltapike so while deltaspike builds fine with 3.1.9, its 
not effectively usable.  An issue was raised with Weld long time back, its been 
noted by others also occurring on wildfly.  So users at the moment best I can 
tell are using 3.1.6 still.  I'll try to get some more details and open a new 
ticket if needed once I do.

> Deltaspike fails with weld 3.1.7+
> -
>
> Key: DELTASPIKE-1448
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1448
> Project: DeltaSpike
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Reporter: Jeremy Landis
>Assignee: Mark Struberg
>Priority: Major
>
> See [https://issues.redhat.com/browse/WELD-2669]
>  
> Since weld 3.1.7, proxy changed.  deltaspike does not work.  Using jdk 11 and 
> now jdk 17.  Projects without deltaspike work fine.  This issue presents 
> itself only with deltaspike usage.  Please confirm that deltaspike works with 
> recent version as weld keeps moving but deltaspike seems tuck in time.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (DELTASPIKE-1448) Deltaspike fails with weld 3.1.7+

[Jeremy Landis (Jira)]

Jeremy Landis created DELTASPIKE-1448:
-

 Summary: Deltaspike fails with weld 3.1.7+
 Key: DELTASPIKE-1448
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1448
 Project: DeltaSpike
  Issue Type: Bug
  Security Level: public (Regular issues)
Reporter: Jeremy Landis


See [https://issues.redhat.com/browse/WELD-2669]

 

Since weld 3.1.7, proxy changed.  deltaspike does not work.  Using jdk 11 and 
now jdk 17.  Projects without deltaspike work fine.  This issue presents itself 
only with deltaspike usage.  Please confirm that deltaspike works with recent 
version as weld keeps moving but deltaspike seems tuck in time.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)