[
https://issues.jboss.org/browse/JBIDE-9116?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-9116:
----------------------------------------------
After all, it is cache in our code that is responsible for the problem. We check that
project is synchronized at least for one level, before loading or rejecting JSF nature.
Removed project remained in cache and when imported again, check for synchronization was
missed, and project was decided as ready by its presence in the cache.
JSF nature is removed after importing JSF project.
--------------------------------------------------
Key: JBIDE-9116
URL:
https://issues.jboss.org/browse/JBIDE-9116
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Priority: Critical
Fix For: 3.3.0.M3
EXECUTE: Create JSF 2 KickStart project.
EXECUTE: Delete this project (don't delete project contents on disk).
EXECUTE: Import this project as an existing project.
FAILURE: See Eclipse log: "Project P/<projectName> has corrupted nature:
org.jboss.tools.jsf.jsfnature"
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira