[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Unable to create a platform agnostic target

This sounds like PDE-UI bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=230146 which has been fixed for RC1.

Tom



Inactive hide details for Thomas Hallgren ---05/13/2008 03:34:24 AM---In Eclipse 3.3, after I installed the RCP delta-pack, allThomas Hallgren ---05/13/2008 03:34:24 AM---In Eclipse 3.3, after I installed the RCP delta-pack, all installed


From:

Thomas Hallgren <thomas@xxxxxxx>

To:

Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

Cc:

Karel Brezina <karel.brezina@xxxxxxxxxxxxxx>

Date:

05/13/2008 03:34 AM

Subject:

[equinox-dev] Unable to create a platform agnostic target




In Eclipse 3.3, after I installed the RCP delta-pack, all installed
plug-ins would be visible on the "Plug-ins" tab under "Preferences" ->
"Plug-in Development" -> "Target Platform", including those not
designated for the current os/ws/arch. In Eclipse 3.4, this list is
filtered. The same seems to be true for the
PluginModelManager.getActiveModels().

I just wonder if this difference is deliberate and if so, what methods I
should use in order to get "all installed" plug-ins, not just the
filtered ones.

The consequence at present is that when Buckminster attempts to set-up a
platform agnostic workspace and is unable to find the filtered plug-ins
in the target platform, it instead downloads them from the update site
and imports them into the workspace. It works, but the approach taken in
3.3 with the delta-pack installed was a lot faster.

Regards,
Thomas Hallgren


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

GIF image

GIF image