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

[Simon Scholz <simon.scholz@xxxxxxxxxxx>]

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 <mistria@xxxxxxxxxx> 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@xxxxxxxxxxx
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@xxxxxxxxxxx
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.scholz@xxxxxxxxxxx, Web: http://www.vogella.com