Bug 379755

Description Troy Bishop 2012-05-16 16:24:02 EDT

Build Identifier: 

This is a follow-on concern to the problem reported in bug 336403.

The process to build a JPA project is now done in a background job (Build JPA Projects) but in the context of a workspace lock, as mentioned in bug 336403 comment 19.  This prevents the immediate UI hang from happening when a JPA project is expanded to show the 'JPA Content' node; however, the UI hang is now delayed until a user attempts to do any UI action which locks on any object in the workspace, for example, save a Java file.  The UI will now display the 'User Operating is Waiting' dialog showing the various jobs that are executing (which is better than the UI hang that previous happened); however, it effectively means a user cannot do anything useful in the product until the 'Build JPA Projects' job is complete.

It would be really nice to have a finer-grained locking mechanism for the 'Build JPA Projects' job so that the UI is not locked for, potentially, a very long period of time.

Reproducible: Always

Steps to Reproduce:
1.  Import a JPA project into the workspace that has a large amount of JAR files on the build path.
2. Expand the project to initiate the 'Build JPA Projects' job.
3. Attempt to save a Java file in that project.  You will now be presented the 'User Operating is Waiting' dialog until the 'Build JPA Projects' job completes (which can be a significant amount of time, i.e. many minutes, depending on the amount of content on the build path).