[
https://issues.jboss.org/browse/JBIDE-10601?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich commented on JBIDE-10601:
-----------------------------------------------
Current implementation of EclipseUtil.getCompilationUnit(IFile) returns handle-only object
which may or may not exist. All clients of this method expected either compilation unit
existing in Java model, or null; which was provided by the method earlier versions.
Creating handle object that may not exist requires check result.exists(), but I do not
think we need that because it is a waste of time and memory.
Failures at processing compilation units excluded from class path
-----------------------------------------------------------------
Key: JBIDE-10601
URL:
https://issues.jboss.org/browse/JBIDE-10601
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI, common/jst/core
Affects Versions: 3.3.0.M5
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Priority: Critical
Fix For: 3.3.0.Beta1
Attachments: Exception.txt
EXECUTE: Create a CDI (can be JSF2 or Seam project as well).
EXECUTE: Create a bean class in Java Source folder 'src'.
ASSERT: File .classpath has entry
{code}
<classpathentry kind="src" path="src"/>
{code}
EXECUTE: Rebuild the project and make sure that everything is alright yet.
EXECUTE: Open project properties -> Java Build Path -> Source, select and expand
Java Source folder in question, navigate to the node 'Excluded (None)', run
'Edit...' and add exclusion pattern "**".
ASSERT: File .classpath has entry
{code}
<classpathentry excluding="**" kind="src"
path="src"/>
{code}
EXECUTE: Run Clean/Build of the project.
FAILURE: Java Model Exception (attached).
--
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