Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Thomas Watson]

> 
> I think this is also something, which should be fixed directly in 
> the code, which reads or parses the /configuration/org.eclipse.osgi/
> framework.info.{x} file.
> 
> Regards,
> 
> Simon
> 

The OSGi framework is behaving exactly the way you told it to.  There is 
no bug in the framework here.  You persistently started the bundle with 
Bundle.start().  The framework cannot simply ignore that on a restart.  It 
must eagerly start the persitently started bundle on restart.  To do 
otherwise will cause the framework implementation to be non-compliant with 
the specification.

Tom


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Etienne Studer]

Hi Marcel

On 23.09.2015, at 11:55, Marcel Bruch  wrote:

> Hi Etienne,
> 
>> Since then, Buildship has been downloaded about 10’000 times but only 2 
>> people reported a problem 
> 
> 
> Well, I think this is not a strong indication for two reasons:
> Eclipse-IDE-wide we see more than half a million submitted (automated) error 
> reports in the last quarter - which boil down to twenty-thousand distinct 
> problematic locations in source code. Most of them are NullPointerExceptions. 
> How many of them have been reported before? 
> I also doubt that many users relate the disappearance of the dialog with 
> Buildship, thus, rather blame Eclipse than Buildship. It’s a subtile but 
> annoying bug.
Very true.


> Besides that:
> * I weight the cost of a respin much lower than the annoyance users might 
> experience 
> * I now understand that this issue occurs for Gradle users only (thanks for 
> explaining) - but for all of them. As of today 10.000 users got affected by 
> it. From October to February (Mars.1) 10.000 * x users will get affected by 
> it again. This is a fair amount of users IMHO.
> * I assume Buildship would prefer to ship the fixed version (maybe I’m wrong).

I fully agree with all your points.


> So far the discussion has been lead by a handful people - which likely is not 
> representative for all opinions.
> If I summarize correctly: David is fine with keeping it "as is“, Mikael 
> want’s a respin. I second Mikaels position.
> Maybe others have no strong feelings or don’t care.

I would like to have a respin with the fix in there, too.


> It’s not on me to push a decision. But I’ve a clear preference - pro our 
> users and pro Buildship.

Thanks for your involvement, Marcel.

Regards, Etienne


> 
> Marcel
> 
> 
> 
>> Am 23.09.2015 um 11:28 schrieb Etienne Studer :
>> 
>> Hi Marcel
>> 
>> Only Buildship users that have launched at least one Gradle task from the 
>> Tasks View may be affected. And, even then, only two users have reported a 
>> problem with the workspace prompt so far.
>> 
>> Please note that we introduced the call to bundle.start() on June 6th. Since 
>> then, Buildship has been downloaded about 10’000 times, but only 2 people 
>> reported a problem with the workspace prompt (if that serves as any kind of 
>> indication).
>> 
>> Etienne
>> 
>> 
>> On 23.09.2015, at 10:11, Marcel Bruch  wrote:
>> 
>>> I commented on the linked bug and currently strongly disagree with David’s 
>>> opinion.
>>> 
>>> 
>>> Short: 
>>> If every Eclipse user using the Java, Java EE, or RCP/RAP EPP Package is 
>>> affected by this, then its no doubt a blocker. 
>>> Then, I vote for a rebuild (and if necessary for postponing the release if 
>>> necessary - just to make clear how strong I feel about it).
>>> 
>>> If not every Java, Java EE, or RCP/RAP EPP Package user is affected by it, 
>>> I’d like to understand when this issue occurs - and when it doesn’t.
>>> 
>>> Follow-ups in Bugzilla.
>>> Marcel
>>> 
>>> 
>>> 
>>> 
 Am 23.09.2015 um 09:27 schrieb Mickael Istria :
 
 My favourite NetBeans troll couldn't miss this opportunity 
 https://twitter.com/ehsavoie/status/646583406176960512
 Tha and my regular chats with various IDE users (I spend a few hours 
 monthly trying to convince IntelliJ and NetBeans users that Eclipse IDE 
 isn't that bad)  make me feel that this issue is "reputation busting 
 embarrassing".  At least, I don't know how I could keep on evangelizing 
 about Eclipse IDE if our community is OK to ship a major bug in a high 
 visible project to its users.
 The bar of quality expectation has raised, IntelliJ and NetBeans are doing 
 a great job, shipping applications that seem mostly bug-free. If we want 
 Eclipse IDE to stay relevant we cannot ship applications with a critical 
 bug.
 -- 
 Mickael Istria
 Eclipse developer at JBoss, by Red Hat
 My blog - My Tweets
 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe 
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>> 
>>> -- 
>>> Codetrails GmbH
>>> The knowledge transfer company
>>> 
>>> Robert-Bosch-Str. 7, 64293 Darmstadt
>>> Phone: +49-6151-276-7092
>>> Mobile: +49-179-131-7721
>>> http://www.codetrails.com/
>>> 
>>> Managing Director: Dr. Marcel Bruch
>>> Handelsregister: Darmstadt HRB 91940
>>> 
>>> ___
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe 
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>> 
>> 

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Martin Lippert]

Hey!

Strong +1 for a re-spin.

Cheers,
-Martin



> Am 23.09.2015 um 12:04 schrieb Simon Scholz :
> 
> Hi,
> 
> the steps to reproduce the issue are:
> 
> 1) Install Buildship with the version you want to test
> 2) Create a new gradle project
> 
> 
> 
> 
> 3) Go to the "Gradle Tasks" view and run a gradle task (e.g. the "clean" task)
> 
> 
> 4) Close the Eclipse IDE and start it again
> 5) The workspace prompt might not be shown any more
> 
> In step 3) the Bundle#start() mehtod is called, which causes OSGi to corrupt 
> the /configuration/org.eclipse.osgi/framework.info.{x} file somehow. The 
> problem in the /configuration/org.eclipse.osgi/framework.info.{x} file then 
> causes that the workspace prompt is not shown any more.
> 
> We were not able to analyse the concrete failure in 
> /configuration/org.eclipse.osgi/framework.info.{x}. 
> But this does not happen always so that might not occur on some machines. So 
> we guess it might depend on a certain OSGi configuration.
> If someone is aware how the 
> /configuration/org.eclipse.osgi/framework.info.{x} actually works, this would 
> help a lot.
> 
> For version 1.0.5 of Buildship, I inserted a check, if the UI Plugin, which 
> is started explicitly by step 3), is already active and also added the 
> "Bundle.START_TRANSIENT" flag, which was suggested by Thomas Watson 
> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=478054#c3). The result of this 
> is that the /configuration/org.eclipse.osgi/framework.info.{x} stays 
> untouched in version 1.0.5 of Buildship.
> 
> I think this is also something, which should be fixed directly in the code, 
> which reads or parses the /configuration/org.eclipse.osgi/framework.info.{x} 
> file.
> 
> Regards,
> 
> Simon
> 
> 
> On 23.09.2015 11:16, Etienne Studer wrote:
>> This bug only reveals itself under certain conditions (otherwise it would 
>> have been detected/reported a long time ago). Simon was able to reproduce 
>> it. Simon, can you please describe the steps here. Thanks.
>> 
>> Etienne
>> 
>> 
>> On 23.09.2015, at 11:11, Mickael Istria  wrote:
>> 
>>> On 09/23/2015 11:09 AM, Etienne Studer wrote:
 Hi Mickael
 
 The bug discovered by the user recently has been there for months. It is 
 just that nobody every experienced/reported that bug. Thus, the bug is in 
 all versions of Buildship < 1.0.5.
 In RC4, we ship Buildship 1.0.3. The fact that the version shows 
 1.0.2.something was a mistake on our side to bump of the version in time 
 for the 1.0.3 release.
>>> Ok, so we'll need steps to reproduce then. Since taking an EPP Java Package 
>>> (with BuildShip installed) and starting it prompts for workspace.
>>> -- 
>>> Mickael Istria
>>> Eclipse developer at JBoss, by Red Hat
>>> My blog - My Tweets
>>> ___
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe 
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>> 
>> 
>> 
>> ___
>> cross-project-issues-dev mailing list
>> 
>> cross-project-issues-dev@eclipse.org
>> 
>> To change your delivery options, retrieve your password, or unsubscribe from 
>> this list, visit
>> 
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 
> -- 
> Trainer, Consultant and Developer
> 
> vogella GmbH
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Tel (040) 78804360, Fax (032) 221739404, Email: 
> simon.sch...@vogella.com, Web: http://www.vogella.com 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Ed Willink]

Hi

[I'm not clear why a new product is a problem with a 'maintenance' 
release; I guess I've become too accustomed to traditional Eclipse 
practices..]


But given that it is there, this seems to be exactly why we have a quiet 
week. Let's fix it. The fix seems very low risk, and conversely the 
non-fix has high reputational impact.


+1 for a respin.

Regards

Ed Willink

On 23/09/2015 11:08, Martin Lippert wrote:

Hey!

Strong +1 for a re-spin.

Cheers,
-Martin




Am 23.09.2015 um 12:04 schrieb Simon Scholz :

Hi,

the steps to reproduce the issue are:

1) Install Buildship with the version you want to test
2) Create a new gradle project




3) Go to the "Gradle Tasks" view and run a gradle task (e.g. the "clean" task)


4) Close the Eclipse IDE and start it again
5) The workspace prompt might not be shown any more

In step 3) the Bundle#start() mehtod is called, which causes OSGi to corrupt 
the /configuration/org.eclipse.osgi/framework.info.{x} file somehow. The 
problem in the /configuration/org.eclipse.osgi/framework.info.{x} file then 
causes that the workspace prompt is not shown any more.

We were not able to analyse the concrete failure in 
/configuration/org.eclipse.osgi/framework.info.{x}.
But this does not happen always so that might not occur on some machines. So we 
guess it might depend on a certain OSGi configuration.
If someone is aware how the /configuration/org.eclipse.osgi/framework.info.{x} 
actually works, this would help a lot.

For version 1.0.5 of Buildship, I inserted a check, if the UI Plugin, which is started 
explicitly by step 3), is already active and also added the 
"Bundle.START_TRANSIENT" flag, which was suggested by Thomas Watson 
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=478054#c3). The result of this is that the 
/configuration/org.eclipse.osgi/framework.info.{x} stays untouched in version 1.0.5 of 
Buildship.

I think this is also something, which should be fixed directly in the code, 
which reads or parses the /configuration/org.eclipse.osgi/framework.info.{x} 
file.

Regards,

Simon


On 23.09.2015 11:16, Etienne Studer wrote:

This bug only reveals itself under certain conditions (otherwise it would have 
been detected/reported a long time ago). Simon was able to reproduce it. Simon, 
can you please describe the steps here. Thanks.

Etienne


On 23.09.2015, at 11:11, Mickael Istria  wrote:


On 09/23/2015 11:09 AM, Etienne Studer wrote:

Hi Mickael

The bug discovered by the user recently has been there for months. It is just that 
nobody every experienced/reported that bug. Thus, the bug is in all versions of 
Buildship < 1.0.5.
In RC4, we ship Buildship 1.0.3. The fact that the version shows 
1.0.2.something was a mistake on our side to bump of the version in time for 
the 1.0.3 release.

Ok, so we'll need steps to reproduce then. Since taking an EPP Java Package 
(with BuildShip installed) and starting it prompts for workspace.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



___
cross-project-issues-dev mailing list

cross-project-issues-dev@eclipse.org

To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Trainer, Consultant and Developer

vogella GmbH
Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Tel (040) 78804360, Fax (032) 221739404, Email:
simon.sch...@vogella.com, Web: http://www.vogella.com
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.6140 / Virus Database: 4419/10687 - Release Date: 09/23/15






___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Mickael Istria]

On 09/23/2015 11:55 AM, Marcel Bruch wrote:

Well, I think this is not a strong indication for two reasons:

 1. Eclipse-IDE-wide we see more than half a million submitted
(automated) error reports in the last quarter - which boil down to
twenty-thousand distinct problematic locations in source code.
Most of them are NullPointerExceptions. How many of them have been
reported before?
 2. I also doubt that many users relate the disappearance of the
dialog with Buildship, thus, rather blame Eclipse than Buildship.
It’s a subtile but annoying bug.

Also, we already had this issue of missing workspace pop-up in JBoss 
Tools, and in case one doesn't switch between workspaces, it's actually 
easily un-noticed or noticed long after the issue is introduced.


--
Mickael Istria
Eclipse developer at JBoss, by Red Hat 
My blog  - My Tweets 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Doug Schaefer]

On 2015-09-23, 8:41 AM, "cross-project-issues-dev-boun...@eclipse.org on
behalf of Ed Willink"  wrote:

>Hi
>
>[I'm not clear why a new product is a problem with a 'maintenance'
>release; I guess I've become too accustomed to traditional Eclipse
>practices..]

Or you missed the memo that these aren¹t maintenance releases anymore.
Another sign we really need to improve our communication around this.

Doug

>
>But given that it is there, this seems to be exactly why we have a quiet
>week. Let's fix it. The fix seems very low risk, and conversely the
>non-fix has high reputational impact.
>
>+1 for a respin.
>
> Regards
>
> Ed Willink
>
>On 23/09/2015 11:08, Martin Lippert wrote:
>> Hey!
>>
>> Strong +1 for a re-spin.
>>
>> Cheers,
>> -Martin
>>
>>
>>
>>> Am 23.09.2015 um 12:04 schrieb Simon Scholz :
>>>
>>> Hi,
>>>
>>> the steps to reproduce the issue are:
>>>
>>> 1) Install Buildship with the version you want to test
>>> 2) Create a new gradle project
>>>
>>> 
>>> 
>>>
>>> 3) Go to the "Gradle Tasks" view and run a gradle task (e.g. the
>>>"clean" task)
>>> 
>>>
>>> 4) Close the Eclipse IDE and start it again
>>> 5) The workspace prompt might not be shown any more
>>>
>>> In step 3) the Bundle#start() mehtod is called, which causes OSGi to
>>>corrupt the /configuration/org.eclipse.osgi/framework.info.{x} file
>>>somehow. The problem in the
>>>/configuration/org.eclipse.osgi/framework.info.{x} file then causes
>>>that the workspace prompt is not shown any more.
>>>
>>> We were not able to analyse the concrete failure in
>>>/configuration/org.eclipse.osgi/framework.info.{x}.
>>> But this does not happen always so that might not occur on some
>>>machines. So we guess it might depend on a certain OSGi configuration.
>>> If someone is aware how the
>>>/configuration/org.eclipse.osgi/framework.info.{x} actually works, this
>>>would help a lot.
>>>
>>> For version 1.0.5 of Buildship, I inserted a check, if the UI Plugin,
>>>which is started explicitly by step 3), is already active and also
>>>added the "Bundle.START_TRANSIENT" flag, which was suggested by Thomas
>>>Watson (https://bugs.eclipse.org/bugs/show_bug.cgi?id=478054#c3). The
>>>result of this is that the
>>>/configuration/org.eclipse.osgi/framework.info.{x} stays untouched in
>>>version 1.0.5 of Buildship.
>>>
>>> I think this is also something, which should be fixed directly in the
>>>code, which reads or parses the
>>>/configuration/org.eclipse.osgi/framework.info.{x} file.
>>>
>>> Regards,
>>>
>>> Simon
>>>
>>>
>>> On 23.09.2015 11:16, Etienne Studer wrote:
 This bug only reveals itself under certain conditions (otherwise it
would have been detected/reported a long time ago). Simon was able to
reproduce it. Simon, can you please describe the steps here. Thanks.

 Etienne


 On 23.09.2015, at 11:11, Mickael Istria  wrote:

> On 09/23/2015 11:09 AM, Etienne Studer wrote:
>> Hi Mickael
>>
>> The bug discovered by the user recently has been there for months.
>>It is just that nobody every experienced/reported that bug. Thus,
>>the bug is in all versions of Buildship < 1.0.5.
>> In RC4, we ship Buildship 1.0.3. The fact that the version shows
>>1.0.2.something was a mistake on our side to bump of the version in
>>time for the 1.0.3 release.
> Ok, so we'll need steps to reproduce then. Since taking an EPP Java
>Package (with BuildShip installed) and starting it prompts for
>workspace.
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or
>unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


 ___
 cross-project-issues-dev mailing list

 cross-project-issues-dev@eclipse.org

 To change your delivery options, retrieve your password, or
unsubscribe from this list, visit

 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>> -- 
>>> Trainer, Consultant and Developer
>>>
>>> vogella GmbH
>>> Haindaalwisch 17a, 22395 Hamburg
>>> Amtsgericht Hamburg: HRB 127058
>>> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
>>> USt-IdNr.: DE284122352
>>> Tel (040) 78804360, Fax (032) 221739404, Email:
>>> simon.sch...@vogella.com, Web: http://www.vogella.com
>>> ___
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@eclipse.org
>>> To change your delivery options, retrieve your password, or
>>>unsubscribe from this list, visit
>>> 

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Doug Schaefer]

OK, I’m awake and have a coffee on the go. As the PMC rep to the planning 
council I’ll be +1’ing the request and passing it along to the planning council 
who are ultimately the ones who decide whether there’s a respin.

But before they do that, I want to make a couple of points and ask for your 
help.

First, we’re having this discussion because we found this issue now and not 
next week. In a sense, we’re lucky we’re in a position to fix this before the 
release. Even if it pushes back the release by a week, which it will.

We need a plan to mitigate these issues no matter when they happen and we 
should have the technology to do it. Projects need the ability to release 
maintenance releases any time and have those releases picked up with an 
Automatic Check for Updates in the EPP packages. We’ve talked about this in the 
Architecture Council and need your help to make sure this works and that the 
projects and packages are structured properly to make sure it works.

BTW, I’m glad the community on cross-projects has spoken on this. It’s great 
input to the planning council who ultimately makes the decision. And that 
decision hasn’t been made yet, so there’s still hope :). We’re a bunch of 
engineers making product decisions, but we’ll try our best.

Doug

From: 
<cross-project-issues-dev-boun...@eclipse.org<mailto:cross-project-issues-dev-boun...@eclipse.org>>
 on behalf of Etienne Studer <etie...@gradle.com<mailto:etie...@gradle.com>>
Reply-To: Cross project issues 
<cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org>>
Date: Wednesday, September 23, 2015 at 8:37 AM
To: Cross project issues 
<cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org>>
Subject: Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship 
/ workspace prompt

Fyi, in a separate email to the Tools PMC mailing list, I have requested the 
Tools PMC to approve a re-spin of Mars 1 RC4.

Etienne


On 23.09.2015, at 11:55, Marcel Bruch 
<marcel.br...@codetrails.com<mailto:marcel.br...@codetrails.com>> wrote:

Hi Etienne,

Since then, Buildship has been downloaded about 10’000 times but only 2 people 
reported a problem

Well, I think this is not a strong indication for two reasons:

  1.  Eclipse-IDE-wide we see more than half a million submitted (automated) 
error reports in the last quarter - which boil down to twenty-thousand distinct 
problematic locations in source code. Most of them are NullPointerExceptions. 
How many of them have been reported before?
  2.  I also doubt that many users relate the disappearance of the dialog with 
Buildship, thus, rather blame Eclipse than Buildship. It’s a subtile but 
annoying bug.


Besides that:
* I weight the cost of a respin much lower than the annoyance users might 
experience
* I now understand that this issue occurs for Gradle users only (thanks for 
explaining) - but for all of them. As of today 10.000 users got affected by it. 
From October to February (Mars.1) 10.000 * x users will get affected by it 
again. This is a fair amount of users IMHO.
* I assume Buildship would prefer to ship the fixed version (maybe I’m wrong).


So far the discussion has been lead by a handful people - which likely is not 
representative for all opinions.
If I summarize correctly: David is fine with keeping it "as is“, Mikael want’s 
a respin. I second Mikaels position.
Maybe others have no strong feelings or don’t care.

It’s not on me to push a decision. But I’ve a clear preference - pro our users 
and pro Buildship.

Marcel



Am 23.09.2015 um 11:28 schrieb Etienne Studer 
<etie...@gradle.com<mailto:etie...@gradle.com>>:

Hi Marcel

Only Buildship users that have launched at least one Gradle task from the Tasks 
View may be affected. And, even then, only two users have reported a problem 
with the workspace prompt so far.

Please note that we introduced the call to bundle.start() on June 6th. Since 
then, Buildship has been downloaded about 10’000 times, but only 2 people 
reported a problem with the workspace prompt (if that serves as any kind of 
indication).

Etienne


On 23.09.2015, at 10:11, Marcel Bruch 
<marcel.br...@codetrails.com<mailto:marcel.br...@codetrails.com>> wrote:

I commented on the linked bug and currently strongly disagree with David’s 
opinion.


Short:
If every Eclipse user using the Java, Java EE, or RCP/RAP EPP Package is 
affected by this, then its no doubt a blocker.
Then, I vote for a rebuild (and if necessary for postponing the release if 
necessary - just to make clear how strong I feel about it).

If not every Java, Java EE, or RCP/RAP EPP Package user is affected by it, I’d 
like to understand when this issue occurs - and when it doesn’t.

Follow-ups in Bugzilla.
Marcel




Am 23.09.2015 um 09:27 schrieb Mickael Istria 
<mist...@redhat.com<mailto:mist...@redhat.com>>:

My favourite NetBeans troll coul

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Etienne Studer]

Hi

Dave Williams gave directions on how to proceed with this problem:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=478054

In short, there will be no respin of Mars 1.

Buildship 1.0.5 is available in the marketplace and contains the fix for this 
issue, incl. the contribution from Thomas.

Thanks for everyone’s input and sorry for the disturbance this issue created.

Regards, Etienne



On 22.09.2015, at 19:07, Etienne Studer  wrote:

> Hi
> 
> 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:
> 
> When launching a Gradle build with Buildship 1.0.3, an extension point is 
> used to start the Buildship UI bundle. The code in Buildship which is 
> responsible for starting the Buildship UI bundle is called even when the UI 
> bundle is already active. This causes the 
> /configuration/org.eclipse.osgi/framework.info.{x} file to change into an 
> unstable state, and 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.
> 
> It seems like there is an underlying bug in the 
> org.osgi.framework.Bundle.start() method that causes the 
> /configuration/org.eclipse.osgi/framework.info.{x} to become corrupt when 
> start() is called and the bundle is already "ACTIVE". Unfortunately, we were 
> not able to read the /configuration/org.eclipse.osgi/framework.info.{x} file 
> and thus we were not able to confirm this theory, nor could we figure out 
> what was actually changed with tools like kdiff3.
> 
> How should we proceed from here?
> 
> Kind regards, Etienne
> 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Mickael Istria]

My favourite NetBeans troll couldn't miss this opportunity 
https://twitter.com/ehsavoie/status/646583406176960512
Tha and my regular chats with various IDE users (I spend a few hours 
monthly trying to convince IntelliJ and NetBeans users that Eclipse IDE 
isn't that bad)  make me feel that this issue is "reputation busting 
embarrassing".  At least, I don't know how I could keep on evangelizing 
about Eclipse IDE if our community is OK to ship a major bug in a high 
visible project to its users.
The bar of quality expectation has raised, IntelliJ and NetBeans are 
doing a great job, shipping applications that seem mostly bug-free. If 
we want Eclipse IDE to stay relevant we cannot ship applications with a 
critical bug.

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat 
My blog  - My Tweets 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Mickael Istria]

Hey,

Actually, the RC4 candidate contains BuildShip *1.0.2* which doesn't 
seem to be affected with this blocker bug.
So if there is no blocker bug with BuildShip 1.0.2, I believe there is 
no need to change anything on the SimRel/EPP side.


--
Mickael Istria
Eclipse developer at JBoss, by Red Hat 
My blog  - My Tweets 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Etienne Studer]

Hi Mickael

The bug discovered by the user recently has been there for months. It is just 
that nobody every experienced/reported that bug. Thus, the bug is in all 
versions of Buildship < 1.0.5.

In RC4, we ship Buildship 1.0.3. The fact that the version shows 
1.0.2.something was a mistake on our side to bump of the version in time for 
the 1.0.3 release.

Etienne


On 23.09.2015, at 11:03, Mickael Istria  wrote:

> Hey,
> 
> Actually, the RC4 candidate contains BuildShip *1.0.2* which doesn't seem to 
> be affected with this blocker bug.
> So if there is no blocker bug with BuildShip 1.0.2, I believe there is no 
> need to change anything on the SimRel/EPP side.
> 
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Mickael Istria]

On 09/23/2015 11:09 AM, Etienne Studer wrote:

Hi Mickael

The bug discovered by the user recently has been there for months. It 
is just that nobody every experienced/reported that bug. Thus, the bug 
is in all versions of Buildship < 1.0.5.
In RC4, we ship Buildship 1.0.3. The fact that the version shows 
1.0.2.something was a mistake on our side to bump of the version in 
time for the 1.0.3 release.
Ok, so we'll need steps to reproduce then. Since taking an EPP Java 
Package (with BuildShip installed) and starting it prompts for workspace.

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat 
My blog  - My Tweets 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Marcel Bruch]

I commented on the linked bug and currently strongly disagree with David’s 
opinion.


Short: 
If every Eclipse user using the Java, Java EE, or RCP/RAP EPP Package is 
affected by this, then its no doubt a blocker. 
Then, I vote for a rebuild (and if necessary for postponing the release if 
necessary - just to make clear how strong I feel about it).

If not every Java, Java EE, or RCP/RAP EPP Package user is affected by it, I’d 
like to understand when this issue occurs - and when it doesn’t.

Follow-ups in Bugzilla.
Marcel




> Am 23.09.2015 um 09:27 schrieb Mickael Istria :
> 
> My favourite NetBeans troll couldn't miss this opportunity 
> https://twitter.com/ehsavoie/status/646583406176960512 
> 
> Tha and my regular chats with various IDE users (I spend a few hours monthly 
> trying to convince IntelliJ and NetBeans users that Eclipse IDE isn't that 
> bad)  make me feel that this issue is "reputation busting embarrassing".  At 
> least, I don't know how I could keep on evangelizing about Eclipse IDE if our 
> community is OK to ship a major bug in a high visible project to its users.
> The bar of quality expectation has raised, IntelliJ and NetBeans are doing a 
> great job, shipping applications that seem mostly bug-free. If we want 
> Eclipse IDE to stay relevant we cannot ship applications with a critical bug.
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat 
> My blog  - My Tweets 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Etienne Studer]

This bug only reveals itself under certain conditions (otherwise it would have 
been detected/reported a long time ago). Simon was able to reproduce it. Simon, 
can you please describe the steps here. Thanks.

Etienne


On 23.09.2015, at 11:11, Mickael Istria  wrote:

> On 09/23/2015 11:09 AM, Etienne Studer wrote:
>> Hi Mickael
>> 
>> The bug discovered by the user recently has been there for months. It is 
>> just that nobody every experienced/reported that bug. Thus, the bug is in 
>> all versions of Buildship < 1.0.5.
>> In RC4, we ship Buildship 1.0.3. The fact that the version shows 
>> 1.0.2.something was a mistake on our side to bump of the version in time for 
>> the 1.0.3 release.
> Ok, so we'll need steps to reproduce then. Since taking an EPP Java Package 
> (with BuildShip installed) and starting it prompts for workspace.
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Thomas Watson]

I think the fix in https://bugs.eclipse.org/bugs/show_bug.cgi?id=478054 is 
incorrect.  I added a comment to the defect with the details.

Tom





From:   Etienne Studer <etie...@gradle.com>
To: Cross project issues <cross-project-issues-dev@eclipse.org>
Date:   09/22/2015 12:08 PM
Subject:    [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with 
Buildship   / workspace prompt
Sent by:cross-project-issues-dev-boun...@eclipse.org



Hi

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:

When launching a Gradle build with Buildship 1.0.3, an extension point is 
used to start the Buildship UI bundle. The code in Buildship which is 
responsible for starting the Buildship UI bundle is called even when the 
UI bundle is already active. This causes the 
/configuration/org.eclipse.osgi/framework.info.{x} file to change into an 
unstable state, and 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.

It seems like there is an underlying bug in the 
org.osgi.framework.Bundle.start() method that causes the 
/configuration/org.eclipse.osgi/framework.info.{x} to become corrupt when 
start() is called and the bundle is already "ACTIVE". Unfortunately, we 
were not able to read the 
/configuration/org.eclipse.osgi/framework.info.{x} file and thus we were 
not able to confirm this theory, nor could we figure out what was actually 
changed with tools like kdiff3.

How should we proceed from here?

Kind regards, Etienne
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Etienne Studer]

Hi

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:

When launching a Gradle build with Buildship 1.0.3, an extension point is used 
to start the Buildship UI bundle. The code in Buildship which is responsible 
for starting the Buildship UI bundle is called even when the UI bundle is 
already active. This causes the 
/configuration/org.eclipse.osgi/framework.info.{x} file to change into an 
unstable state, and 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.

It seems like there is an underlying bug in the 
org.osgi.framework.Bundle.start() method that causes the 
/configuration/org.eclipse.osgi/framework.info.{x} to become corrupt when 
start() is called and the bundle is already "ACTIVE". Unfortunately, we were 
not able to read the /configuration/org.eclipse.osgi/framework.info.{x} file 
and thus we were not able to confirm this theory, nor could we figure out what 
was actually changed with tools like kdiff3.

How should we proceed from here?

Kind regards, Etienne

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

[Etienne Studer]

Thanks, Thomas. I have applied your improvement to our fix. It is in Buildship 
1.0.5, released just a few minutes ago.

Regards, Etienne



On 22.09.2015, at 19:56, Thomas Watson <tjwat...@us.ibm.com> wrote:

> I think the fix in https://bugs.eclipse.org/bugs/show_bug.cgi?id=478054is 
> incorrect.  I added a comment to the defect with the details.
> 
> Tom
> 
> 
> 
> 
> 
> From:Etienne Studer <etie...@gradle.com>
> To:Cross project issues <cross-project-issues-dev@eclipse.org>
> Date:    09/22/2015 12:08 PM
> Subject:    [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with 
> Buildship/ workspace prompt
> Sent by:cross-project-issues-dev-boun...@eclipse.org
> 
> 
> 
> Hi
> 
> 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:
> 
> When launching a Gradle build with Buildship 1.0.3, an extension point is 
> used to start the Buildship UI bundle. The code in Buildship which is 
> responsible for starting the Buildship UI bundle is called even when the UI 
> bundle is already active. This causes the 
> /configuration/org.eclipse.osgi/framework.info.{x} file to change into an 
> unstable state, and 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.
> 
> It seems like there is an underlying bug in the 
> org.osgi.framework.Bundle.start() method that causes the 
> /configuration/org.eclipse.osgi/framework.info.{x} to become corrupt when 
> start() is called and the bundle is already "ACTIVE". Unfortunately, we were 
> not able to read the /configuration/org.eclipse.osgi/framework.info.{x} file 
> and thus we were not able to confirm this theory, nor could we figure out 
> what was actually changed with tools like kdiff3.
> 
> How should we proceed from here?
> 
> Kind regards, Etienne
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev