[jira] [Resolved] (DELTASPIKE-1409) ProjectStageTestControlTest doesn't work on Weld2

2020-05-15 Thread Mark Struberg (Jira) 


 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Struberg resolved DELTASPIKE-1409.
---
Resolution: Fixed

> ProjectStageTestControlTest doesn't work on Weld2
> -
>
> Key: DELTASPIKE-1409
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1409
> Project: DeltaSpike
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tests
>Affects Versions: 1.9.3
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.4
>
>
> ProjectStageTestControlTest fails in Weld3. It works fine in Weld1 Weld3 and 
> also works fine in all other containers.
> The problem is that Weld2 interpreted some wording in the spec quite 
> restrictive. If you have an {{}} in a beans.xml and the class is 
> {{@Alternative}} BUT is vetoed via an extension, then many Weld 2 versions 
> blow up. With some old ones it works though.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (DELTASPIKE-1409) ProjectStageTestControlTest doesn't work on Weld2

2020-05-15 Thread ASF subversion and git services (Jira) 


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

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

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

DELTASPIKE-1409 disable test-control tests for Weld2

Weld2 has a problem with handling @Alternative classes which got vetoed.
Those tests work perfectly fine on Weld1, Weld3, OWB (any version) and
various EE containers. It's just broken on Weld2.


> ProjectStageTestControlTest doesn't work on Weld2
> -
>
> Key: DELTASPIKE-1409
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1409
> Project: DeltaSpike
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Tests
>Affects Versions: 1.9.3
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.4
>
>
> ProjectStageTestControlTest fails in Weld3. It works fine in Weld1 Weld3 and 
> also works fine in all other containers.
> The problem is that Weld2 interpreted some wording in the spec quite 
> restrictive. If you have an {{}} in a beans.xml and the class is 
> {{@Alternative}} BUT is vetoed via an extension, then many Weld 2 versions 
> blow up. With some old ones it works though.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (DELTASPIKE-1409) ProjectStageTestControlTest doesn't work on Weld2

2020-05-15 Thread Mark Struberg (Jira) 
Mark Struberg created DELTASPIKE-1409:
-

 Summary: ProjectStageTestControlTest doesn't work on Weld2
 Key: DELTASPIKE-1409
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1409
 Project: DeltaSpike
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Tests
Affects Versions: 1.9.3
Reporter: Mark Struberg
Assignee: Mark Struberg
 Fix For: 1.9.4


ProjectStageTestControlTest fails in Weld3. It works fine in Weld1 Weld3 and 
also works fine in all other containers.

The problem is that Weld2 interpreted some wording in the spec quite 
restrictive. If you have an {{}} in a beans.xml and the class is 
{{@Alternative}} BUT is vetoed via an extension, then many Weld 2 versions blow 
up. With some old ones it works though.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (DELTASPIKE-1408) Some Weld versions fail on CDI.current() depending on the ClassLoader setup

2020-05-15 Thread ASF subversion and git services (Jira) 


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

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

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

DELTASPIKE-1408 in some situations CDI.current() doesn't work in Weld3

So we try a fallback onto CDI-1.0 tricks to resolve the BeanManager.


> Some Weld versions fail on CDI.current() depending on the ClassLoader setup
> ---
>
> Key: DELTASPIKE-1408
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1408
> Project: DeltaSpike
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Core
>Affects Versions: 1.9.3
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.4
>
>
> Weld 3.1.3.Final and others blow up with an internal Exception when calling 
> {{CDI.current()}} in some situations (ClassLoader, boot order, not sure yet).
> What we can rather easily do is to fallback to our classic CDI-1.0 behaviour 
> in this case.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (DELTASPIKE-1408) Some Weld versions fail on CDI.current() depending on the ClassLoader setup

2020-05-15 Thread Mark Struberg (Jira) 
Mark Struberg created DELTASPIKE-1408:
-

 Summary: Some Weld versions fail on CDI.current() depending on the 
ClassLoader setup
 Key: DELTASPIKE-1408
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1408
 Project: DeltaSpike
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Core
Affects Versions: 1.9.3
Reporter: Mark Struberg
Assignee: Mark Struberg
 Fix For: 1.9.4


Weld 3.1.3.Final and others blow up with an internal Exception when calling 
{{CDI.current()}} in some situations (ClassLoader, boot order, not sure yet).

What we can rather easily do is to fallback to our classic CDI-1.0 behaviour in 
this case.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)