[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5948) A lot of exceptions are thorwn by CDI model if user changes source folder.

[Viacheslav Kabanovich (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-5948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12525371#action_12525371 ] 

Viacheslav Kabanovich commented on JBIDE-5948:
----------------------------------------------

When performing incremental build, we need to know which previously loaded sourcepaths are not valid in the latest state of project. Asking the IJavaProject we only can get the list of currently valid sourcepaths, so we have also to keep the list of previously valid sourcepaths to compare them.

> A lot of exceptions are thorwn by CDI model if user changes source folder.
> --------------------------------------------------------------------------
>
>                 Key: JBIDE-5948
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5948
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdi (jsr-299)
>    Affects Versions: 3.1.0.CR2
>            Reporter: Alexey Kazakov
>            Assignee: Viacheslav Kabanovich
>            Priority: Critical
>             Fix For: 3.1.1
>
>         Attachments: .log, Patch5948.patch
>
>
> 1. Create any CDI project (enable CDI support for a java project).
> 2. Build the project.
> 3. Create an alternative source folder.
> 4. Set this new folder as source instead of first one.
> 5. Build the project.
> See Eclipse log. There are a lot of exceptions like Java Model Exception: Java Model Status [JavaSource [in tck] is not on its project's build path]
> See the attached log for details.
> I tested it on CDI TCK project.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira