[
https://issues.jboss.org/browse/JBIDE-26664?page=com.atlassian.jira.plugi...
]
Zbyněk Červinka commented on JBIDE-26664:
-----------------------------------------
I have na update on this issue - in many cases is everything as the description and
screenshot says (CDI 1.1 and JSR-365), but I have found a special case where the JSR for
CDI 1.1 is *{color:#DE350B}JSR-299{color}*. It has been seen in the
*{color:#DE350B}testValidationOfBeanDiscoveryInImplicitArchives(){color}* test in
*{color:#DE350B}BeanDiscoveryInImplicitArchivesTestCDI11{color}*.
h2. See the Screenshot below:
!validationOfBeanDiscoveryInExplicitArchives-test.png|thumbnail!
Wrong JSR specification is shown for CDI 1.2 warning dedicated to
multiple beans eligibility
--------------------------------------------------------------------------------------------
Key: JBIDE-26664
URL:
https://issues.jboss.org/browse/JBIDE-26664
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi
Affects Versions: 4.12.0.AM1
Environment: Fedora 29, OS X 10.14.6, Wildfly 13 + 16
Reporter: Ondrej Dockal
Assignee: Jeff MAURY
Priority: Critical
Fix For: 4.14.x
Attachments: CDI1.1.png, validationOfBeanDiscoveryInExplicitArchives-test.png
Wildfly 13 that contains libs for both cdi 1.2 and 2.0 are wrongly identifying cdi
version (probably) and shows message that is dedicated to 2.0 spec even though that
project nature is defined for cdi 1.2.
See the test, ie:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
I can only see a problem in choosing the cdi version in cdi jbt core or ambiguous options
of cdi libs in wf 13 server.
*UPDATE:* Issue appears also when using WildFly 16
--
This message was sent by Atlassian Jira
(v7.13.8#713008)