Community
Participate
Working Groups
Set Build Automatically false Edit many (e.g 20) MANIFEST.MF or build.properties files, don't Save. Save. The user is locked out waiting for a Workspace Operation. It appears that each save provokes a not-in-background update plugin dependencies, even though build automatically is disabled. Only after one update completes does the next save occur. So there are numerous redundant updates making a not-short lockout unacceptably long.
The new Automatic-Module-Name header quick fix provides a simple repro of this. See Bug 525660
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.