Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » Blocking problems w/a p2 based RCP product-Updates locked/feature install breaks
Blocking problems w/a p2 based RCP product-Updates locked/feature install breaks [message #592353] Wed, 25 February 2009 17:43
Chris Williams is currently offline Chris WilliamsFriend
Messages: 29
Registered: July 2009
Junior Member
I’ve been leading the charge in moving our company's product over to use
Eclipse 3.4 and P2 as our base (and new update mechanism) - we've been
building on top of Eclipse 3.2.2 for two years now and our users are
rightly demanding we move forward. We’ve been running into a number of
issues and oddities in getting the 3.4 based product working properly,
though.

We’re building our product against 3.4 and then using the p2 director app
to generate the standalone product on our build machine. We have the
following hierarchy:
com.aptana.ide.rcp.product
|-com.aptana.ide.feature.rcp
|- com.aptana.ide.feature
|- org.eclipse.platform

We build com.aptana.ide.feature for use when plugging into Eclipse and
generate an update site for that. We build com.aptana.ide.rcp.product as a
product, with an update site. A third build then triggers and uses the
p2.director to generate standalone products from the product build’s
update site. We zip those up per OS/Arch combo (and also re-purpose those
for installers).

There’s been a number of odd issues we’ve run into. Here's the blockers:
- When we specify a custom osgi.configuration.area under the user’s home
directory in the config.ini, the product IU and a “pro” feature we
pre-install are both marked as locked for updates, so even though updates
are found by automatic update check, they’re ignored as invalid.

- If we don’t specify a separate config area we don’t have that issue any
more, but after the first install of any feature via the P2 APIs, the
product won’t start back up again properly. It appears that the config.ini
gets changed and the osgi.bundles property is changed to list the newly
installed plugins (whereas before it pointed to the simpleconfigurator
plugin which used the bundles.info listing).

So, if we specify a custom osgi.configuration area our pre-installed
features and product can't be update. If we don't, then after a feature is
installed the product won't start up all the plugins properly.

-Chris
Previous Topic:Any way to insert SCM revision # as qualifier per plugin/feature not globally?
Next Topic:FYI: Target Platform Changes
Goto Forum:
  


Current Time: Thu Jun 24 10:23:18 GMT 2021

Powered by FUDForum. Page generated in 0.02088 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top