| Thanks, Doug.
Etienne
The respin has been approved and David has it underway.
Sent from my BlackBerry 10 smartphone on the Rogers network.
From: David M Williams
Sent: Wednesday, September 23, 2015 8:42 AM
To: Tools PMC mailing list
Reply To: Tools PMC mailing list
Subject: Re: [tools-pmc] [Request] Respin of Mars 1
|
Doug, as are rep to Planning Council, can you please assess and if you agree should be re-spun, take to the Planning Council. I've already
voiced my opinion ... but there certainly is a lot of noise about it. None of that noise has
changed my view -- I think it's just a "recency effect". I can't help but think it would have been noticed sooner, by more people, if it was all that bad. But ... all my views just means it should go through the formal Exception Process. I'm happy to go along
with what the Planning Council decides (As tell as Tools PMC).
Keep in mind, if we do "re-spin", I'd recommend a 1 week extension of the release date. [Not a great start for our nimble "join late" process.]
Thanks,
From: Etienne Studer <etienne@xxxxxxxxxx>
To: Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>,
Date: 09/23/2015 07:29 AM
Subject: [tools-pmc] [Request] Respin of Mars 1
Sent by: tools-pmc-bounces@xxxxxxxxxxx
Hello
I’d like to ask the Tools PMC to do a re-spin of Mars 1 due to a critical bug in Buildship 1.0.3, the Buildship version that is currently in Mars 1 RC4 and its EPP packages (Java / Committer / RCP). The bug has been fixed in Buildship 1.0.5.
See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=478151
Some details below:
What is the bug?
Buildship calls Bundle#start() to eagerly activate its UI plugin. This is a problem since it causes the OSGi framework to persistently mark that bundle for eager activation upon restart. Once Eclipse is restarted, the bundle that was persistently
activated will be activated very early in the startup process which will likely cause it to touch preferences 'too early' which results in no workspace prompt and the default workspace being used.
See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=478054.
How does the bug become apparent?
Once a Gradle task has been launched from the Tasks View, the user will not be prompted for the workspace anymore the next time he starts Eclipse, but instead the very default Eclipse workspace is used.
Who is affected?
The bug affects those users (and only those users) that run a Gradle task through Buildship from within Eclipse.
When was the bug identified and investigated?
We were able to confirm that this is a Buildship bug yesterday. We also found the cause and a fix yesterday. All Buildship versions < 1.0.5 contain the bug.
When was this bug introduced?
The bug is there since June 6th, as we have found out in retrospect (yesterday).
Why was this bug not found earlier?
Most likely, because the relation between Buildship and how the bug manifests itself in Eclipse is not obvious to the user observing the issue.
Is there a fix available?
Yes, the fix is available in Buildship 1.0.5, available as of last night. It has been confirmed by three Gradle forum users that the issue has been resolved in Buildship 1.0.5 .
I believe that it is critical for the introduction of Buildship into the Eclipse SimRel and the Eclipse distributions that we get this fix in for Mars 1. Otherwise, it will be a bad start for Buildship, especially considering that the bug was
known before the release and a fix would have been available. Also, users might associate the bug with a general Eclipse problem, which could cause unfair frustrations about the Eclipse IDE.
Thanks for considering it.
Regards, Etienne
_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tools-pmc
_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tools-pmc |
