[jbosstools-issues] [JBoss JIRA] (JBIDE-12771) EclipseJavaUtil never evicts its cache when projects are deleted (or their classpath change)

[Fred Bricon (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-12771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Bricon resolved JBIDE-12771.
---------------------------------

    Resolution: Won't Fix


Ok won't fix then. I'll follow Snjeza's suggestion and use IJavaProject.findType() instead.
                
> EclipseJavaUtil never evicts its cache when projects are deleted (or their classpath change)
> --------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-12771
>                 URL: https://issues.jboss.org/browse/JBIDE-12771
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: common/jst/core
>    Affects Versions: 3.3.1
>            Reporter: Fred Bricon
>            Assignee: Fred Bricon
>             Fix For: 4.0.0.Beta1
>
>
> When calling EclipseJavaUtil#findType(javaProject, qualifiedName) we hit a cache of ITypes using the project name has key.
> Problem is, the cache is never updated if the project is deleted, or its classpath changes. This directly causes issues like JBIDE-12727, where we find   an IType entry in a project's classpath which has the same name as a previously deleted project.
> Everything is static in EclipseJavaUtil so we won't be able to implement IElementChangedListener directly. I believe you should had some new method in EclipseJavaUtil, like evict(key), that'd be called by an other IElementChangedListener, registered on plugin startup.

--
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