If you've been experiencing weird behavior with the
[ ] Include items that are installed
checkbox on the p2 Available Software page, can you please help me?

The relevant bug is
https://bugs.eclipse.org/bugs/show_bug.cgi?id=228794

When first reported, I could not reproduce it.
Then I saw it. Today I saw it most of the day while working on something else, and at some point it disappeared.
Now that I try to reproduce it, I don't see it.

So I believe it takes some setup to get into a state where you see the bug.
Or else something has been changing underneath me throughout the day that is affecting it.

Either
- there is some subtle bug in the UI that doesn't always manifest (most likely the case)
- there have been changes over the last few days in how a profile handles queries
- there have been changes over the last few days in how a profile instance is retrieved by id (ie, accidentally getting an out of date profile?)

If anyone has any leads, please annotate the bug.
I'll try again tomorrow with fresh eyes, fresh workspace, fresh build.

thanks,
susan

Never mind...got it.
Funny how the mind thinks of new ideas right after a desperate cry for help.

susan
----- Forwarded by Susan Franklin McCourt/Beaverton/IBM on 04/30/2008 09:53 PM -----

Susan Franklin McCourt 04/30/2008 08:58 PM

To: equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org cc: From: Susan Franklin McCourt/Beaverton/IBM <at> IBMUS Subject: p2 - help me find this bug!

If you've been experiencing weird behavior with the
[ ] Include items that are installed
checkbox on the p2 Available Software page, can you please help me?

The relevant bug is
https://bugs.eclipse.org/bugs/show_bug.cgi?id=228794

When first reported, I could not reproduce it.
Then I saw it. Today I saw it most of the day while working on something else, and at some point it disappeared.
Now that I try to reproduce it, I don't see it.

So I believe it takes some setup to get into a state where you see the bug.
Or else something has been changing underneath me throughout the day that is affecting it.

Either
- there is some subtle bug in the UI that doesn't always manifest (most likely the case)
- there have been changes over the last few days in how a profile handles queries
- there have been changes over the last few days in how a profile instance is retrieved by id (ie, accidentally getting an out of date profile?)

If anyone has any leads, please annotate the bug.
I'll try again tomorrow with fresh eyes, fresh workspace, fresh build.

thanks,
susan

I tagged the p2 UI projects for the 1am build.

The map file has been updated for the following Bug changes:
+ Bug 228794. [ui] "Include items that have already been installed" checkbox does not work properly (FIXED)
+ Bug 229305. [ui] Installing from a filtered selection does not work (FIXED)

The following projects have changed:
org.eclipse.equinox.p2.ui

susan

_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@...
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev

Please open a bug if you think you have found a regression. In the bug report please give steps to reproduce. Thanks.

If you launch with the option command line option -noExit that should help keep the framework running when the application fails.

Tom



"David Leangen" ---05/01/2008 02:30:03 AM---Hello!

From:	"David Leangen" <osgi-9kIQqJcmqRTR7s880joybQ@public.gmane.org>
To:	<equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>
Date:	05/01/2008 02:30 AM
Subject:	[equinox-dev] New version of Equinox quits upon bundle error

Hello!

I recently updated to 3.4M6, which IIUC is the most recent release.

I run my apps in the Eclipse console because it is great for debugging.
However, with this version, when one of my bundles has an error, everything
shuts down with a message "The Application could not start...".


How can I get the console to work like before and just run with the
erroneous bundles in a RESOLVED state so I can debug the problems?


BTW, the error logs are complaining that I need
org.eclipse.equinox.core.runtime installed. I don't mind installing one
bundle, but that bundle has lots of dependencies that I don't want.

I never needed this before... so what's changed?



Thank you!
David


_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

More information is needed on how you are launching Equinox, including what bundles you are using and what config.ini options etc. Also, what version of Eclipse you are migrating from where your application worked. Lets move this discussion into a bug report. If you have an application that used to work in 3.2-3.3 and now does not work in 3.4 then that is the bug you should open with a description of how to reproduce or even better would be a testcase for us to reproduce. I would open that bug against Equinox->Bundles

In 3.3 we split the application container out of org.eclipse.core.runtime into org.eclipse.equinox.app. You must include the org.eclipse.equinox.app bundle in your configuration to use the Eclipse application container.

Hope we can help you out.

Tom



"David Leangen" ---05/01/2008 09:06:01 AM---Thank you, Tom,

From:	"David Leangen" <osgi-9kIQqJcmqRTR7s880joybQ@public.gmane.org>
To:	"Equinox development mailing list" <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>
Date:	05/01/2008 09:06 AM
Subject:	RE: [equinox-dev] New version of Equinox quits upon bundle error

Thank you, Tom,

What would the bug be, then? "Running in console requires
org.eclipse.equinox.core.runtime"? It is my understanding that only the osgi
package should be required.


BTW, when I add the -noExit option, I get an error (Unrecognized option). Is
that really a valid option?


Regards,
David


-----Original Message-----
From: equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
[mailto:equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@public.gmane.org]On Behalf Of Thomas Watson
Sent: 1 May 2008 22:17
To: Equinox development mailing list
Subject: Re: [equinox-dev] New version of Equinox quits upon bundle error


Please open a bug if you think you have found a regression. In the bug
report please give steps to reproduce. Thanks.

If you launch with the option command line option -noExit that should help
keep the framework running when the application fails.

Tom



"David Leangen" ---05/01/2008 02:30:03 AM---Hello!


From:
"David Leangen" <osgi-9kIQqJcmqRTR7s880joybQ@public.gmane.org>

To:
<equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>

Date:
05/01/2008 02:30 AM

Subject:
[equinox-dev] New version of Equinox quits upon bundle error







Hello!

I recently updated to 3.4M6, which IIUC is the most recent release.

I run my apps in the Eclipse console because it is great for debugging.
However, with this version, when one of my bundles has an error, everything
shuts down with a message "The Application could not start...".


How can I get the console to work like before and just run with the
erroneous bundles in a RESOLVED state so I can debug the problems?


BTW, the error logs are complaining that I need
org.eclipse.equinox.core.runtime installed. I don't mind installing one
bundle, but that bundle has lots of dependencies that I don't want.

I never needed this before... so what's changed?



Thank you!
David


_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

The map file has been updated for the following Bug changes:
+ Bug 229641. Added Extension location repos in UI contain no features (FIXED)
+ Bug 229722. NPE loading update site at tikalk.com (FIXED)
+ Bug 229778. Use application as a trigger to disable the configuration application (FIXED)

The following projects have changed:
org.eclipse.equinox.p2.metadata.generator
org.eclipse.equinox.p2.extensionlocation
org.eclipse.equinox.p2.reconciler.dropins
org.eclipse.equinox.p2.tests

p2 now supports feature patches, so a feature patch can be used to replace a plug-in in the base platform. However, we didn't get to our desired goal of spoofing up patches automatically if the user dropped in a new version of the bundle in dropins. Here is the bug report where you can follow progress on this:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=222945

John

Scott Lewis <slewis-moQcexxCXgLby3iVrkZq2A@public.gmane.org> Sent by: equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@public.gmane.org 04/28/2008 11:48 PM Please respond to Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>

To Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org> cc Subject [equinox-dev] [prov] handing of patches

With the recent changes/additions for patch handling, will p2 now allow
the update/patch of platform plugins (including, for example, ECF6)?

Reason I ask...ECF currently has to create separate builds (and ask
people to use different update sites) for ECF-on-eclipse 3.3-3.4M5, and
ECF-on-eclipse 3.4M6+ because of the p2 'patch problem'.  Just want to
know if this is still an issue (my expectation is yes this is still an
issue, but would like to be sure).

Thanks,

Scott






_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev

That said, I believe that ECF's situation is still relatively exceptional in that it is now split between the platform and its own feature, and that ECF should not be delivered by patches and that the platform should just require ECF.

John Arthorne---05/01/2008 02:34:45 PM---p2 now supports feature patches, so a feature patch can be used to replace a plug-in in the base platform. However, we didn't g

From:	John Arthorne/Ottawa/IBM <at> IBMCA
To:	Equinox development mailing list <equinox-dev <at> eclipse.org>
Date:	05/01/2008 02:34 PM
Subject:	Re: [equinox-dev] [prov] handing of patches

p2 now supports feature patches, so a feature patch can be used to replace a plug-in in the base platform. However, we didn't get to our desired goal of spoofing up patches automatically if the user dropped in a new version of the bundle in dropins. Here is the bug report where you can follow progress on this:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=222945

John

Scott Lewis <slewis-moQcexxCXgLby3iVrkZq2A@public.gmane.org> Sent by: equinox-dev-bounces-j9T/66MeVpFAfugRpC6u6w@public.gmane.org 04/28/2008 11:48 PM Please respond to Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org>

To Equinox development mailing list <equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org> cc Subject [equinox-dev] [prov] handing of patches

With the recent changes/additions for patch handling, will p2 now allow
the update/patch of platform plugins (including, for example, ECF6)?

Reason I ask...ECF currently has to create separate builds (and ask
people to use different update sites) for ECF-on-eclipse 3.3-3.4M5, and
ECF-on-eclipse 3.4M6+ because of the p2 'patch problem'.  Just want to
know if this is still an issue (my expectation is yes this is still an
issue, but would like to be sure).

Thanks,

Scott






_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev-j9T/66MeVpFAfugRpC6u6w@public.gmane.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev