[ https://issues.jboss.org/browse/JBIDE-8563?page=com.atlassian.jira.plugin... ] José Freitas updated JBIDE-8563: -------------------------------- Workaround Description: there's no need for a workaround since the app runs fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8563?page=com.atlassian.jira.plugin... ] Alexey Kazakov commented on JBIDE-8563: --------------------------------------- What I do: 1. get clone https://github.com/seam/examples/ Seam-examples 2. Open Eclipse/JBT. File->Import->Maven->Existing Maven Project->.../Seam-examples. Build the project. 3. No any errors in booking/src/main/webapp/WEB-INF/beans.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8563?page=com.atlassian.jira.plugin... ] José Freitas commented on JBIDE-8563: ------------------------------------- You did the same thing I usually do, yet I had this problem in two enviroments, one at my home, and one at my work. As you suggested trying, cleaning the project made the error disappear, but at home I had to clean it two times, and I had the impression that on second time it worked after clearing the error log view(I wanted to see if it was throwing something new). Another detail I noticed: when the error is there, the Ctrl+space don´t bring the class too. I tried again two more times from the beggining (delete everything and cloned the repo again) and the error don´t appear anymore. Sorry for not being able to collect any more data, maybe my eclipses just had an insanity moment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8563?page=com.atlassian.jira.plugin... ] Viacheslav Kabanovich commented on JBIDE-8563: ---------------------------------------------- Validator for beans.xml reads class name and asks CDI model for bean with that Java type. Actually, the validator uses DOM model, but it could use XModel, it is not important. CDI model does not return bean object for valid type name, and bean objects are loaded by builder using JDT, so that XModel has nothing to do with it. Since this issue takes place in newly imported Maven projects, I think it happens as follows. 1. Project is imported. It still has no CDI nature. 2. Full Build started. 3. In a separate job, concurring with build, CDI nature and builder are added to the project. 4. Build proceeds to validation, and since project already has CDI nature, CDI validation runs, but CDI model is not built yet. ' Ctrl+space don´t bring the class too' - confirms that there is no bean in CDI model. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8563?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-8563: --------------------------------------- Fix Version/s: 3.3.0.M2 (was: 3.3.0.M1) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8563?page=com.atlassian.jira.plugin... ] Alexey Kazakov resolved JBIDE-8563. ----------------------------------- Fix Version/s: 3.3.0.Beta1 (was: 3.3.x) Resolution: Done I can't reproduce this issue anymore. It seems to be fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira