|
On 09/22/2015 07:07 PM, Etienne Studer
wrote:
In our Gradle
forum, a user recently reported a problem with not seeing
the workspace prompt when starting Eclipse and suspected that it
is related to Buildship. We created a BugZilla
issue for this. After deeper investigations, Simon Scholz
from Vogella GmbH eventually found the problem and a fix:
as a consequence the workspace prompt is not shown anymore when
starting Eclipse. The plugin activation code has been in Buildship
for a very long time but until very recently, nobody had ever
experienced this problem.
[...]
Buildship
1.0.4, built today, contains a patch for this issue by
only starting the UI bundle programmatically if the bundle is
not already in state “ACTIVE". This avoids the corruption
of /configuration/org.eclipse.osgi/framework.info.{x}
and thus the workspace prompt is always properly shown when
starting Eclipse. How should we proceed from here?
Not prompting user for workspace is a critical bug. as many users
deal with multiple workspaces.
IMO, Gradle support is the very new thing of this release, it's even
one of the things that will most likely get advertised as part of
Mars.1. So we can expect that the bug will have a high exposure and
will hurt many users, giving an impression of "the only new thing in
this release causes a blocker bug". This is not something the
Eclipse Community and Eclipse IDE can afford.
There is no doubt this issue requires a respin of Mars.1.
|
