I opened a bug for this issue as it's breaking people's workflows:
     https://bugs.eclipse.org/bugs/show_bug.cgi?id=231799

PDE introduced a new preference to control how the target platform is
built. By default, this preference is set to true and will build your
target platform based on your targets configuration (via the platform.xml
in <3.4, >=3.4 is the bundles.info).

I've been having an internal battle to just turn this preference off by
default instead of the current logic detailed in that bug due to delta pack
issues.

The p2/PDE team will have to come on a convergence on what is best. cc
yourself on the bug and stay tuned

Cheers,

---
Chris Aniszczyk | IBM Lotus | Eclipse Committer |
http://mea-bloga.blogspot.com | +1.860.839.2465


                                                                       
  From:       Thomas Hallgren <[EMAIL PROTECTED]>                         
                                                                       
  To:         Equinox development mailing list <[email protected]>
                                                                       
  Cc:         Karel Brezina <[EMAIL PROTECTED]>             
                                                                       
  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
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev,

<<inline: graycol.gif>>

<<inline: ecblank.gif>>

_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Reply via email to