[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7934) Eclipse hogged when working on a fresh EAR project

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-7934:
------------------------------------

It seems client all classpath container is a large part of this. Would it be reasonable to cache these results based on each runtime? I think that seems like a good idea, since each runtime shouldn't be changing too much... however if someone does change the runtime's configuration or home directory, the cache will be old and I'm not sure there's a good way to verify that. 

I'll have to look into this but right now I'm busy with the deltacloud stuff. 

> Eclipse hogged when working on a fresh EAR project
> --------------------------------------------------
>
>                 Key: JBIDE-7934
>                 URL: https://issues.jboss.org/browse/JBIDE-7934
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.2.0.Beta2
>         Environment: Windows Vista 32 bit
> Eclipse Helios SR1
> JBoss Tools 3.2 Beta 2
>            Reporter: Miroslav Pavleski
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 3.2.0.CR1
>
>         Attachments: stack.txt, stack2.txt, stack3.txt, stack4.txt
>
>
> Once a new project is created and CDI enabled property set on sub-projects everything stops to a crawl and the whole eclipse becomes too slow.
> The issue is manifesting itself with CDI validation off. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira