[
https://issues.jboss.org/browse/JBIDE-12575?page=com.atlassian.jira.plugi...
]
Daniel Azarov commented on JBIDE-12575:
---------------------------------------
I have been tested jbdevstudio-product-eap-universal-6.0.0.CR1-v20121118-2035-B111.jar
What I did:
1. Create CDI project
2. Create CDI Bean:
{code}
package org.jboss.jsr299.tck;
import javax.enterprise.inject.Produces;
import javax.inject.Named;
public class Bean_Broken {
public void foo() {
String s = "#{string.scsscss}";
String s2 = "#{string.bacssd}";
}
@Named
@Produces
public String string() {
return "";
}
}
{code}
3. Open Bean_Broken in Java Editor
4. Change #{string.scsscss} and/or #{string.bacssd}
5. Do not save the file
6. Remove CDI Support
FAIL: Error in error log: Trying to validate P/cdiproject but there is no CDI Nature in
the project.
An exception stack trace is not available.
Problem with CDI validator
--------------------------
Key: JBIDE-12575
URL:
https://issues.jboss.org/browse/JBIDE-12575
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 4.0.0.Alpha1
Reporter: Jaroslav Jankovič
Assignee: Victor Rubezhny
Priority: Minor
Fix For: 4.1.x
Attachments: JBIDE-12575.ogv
There is a problem to force CDI validator to work. In my case, I created simple dynamic
web project without CDI support, added some bean with Multiple beans eligible case
(message not present yet). Add CDI support into project. Expected validation messages
won't appear - cleaning the project doesn't help either.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira