[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Problems updating feature in RCP

Thanks for pointing me in the right direction. I'm still struggling with the difference between the p2 generation from within Eclipse and my PDE build script. But I hope to find the solution soon.


Op 16 Sep 2008, om 14:58 heeft Jeff McAffer het volgende geschreven:

try adding
  -bundlepool ${INSTALL_DIR}

I noticed that the IU you are installing is the feature group. In general it should be the product IU (that is, an IU with the same ID as the product as defined in the .product file. This assumes that you are createing a standalone product. Without this I am a little surprised that the director is giving you an executable and various other root files.


Hendrik Eeckhaut wrote:
Hi p2ers,

I have been struggling to make my RCP-application updatable with P2 and got stuck on following problem:

I made an RCP product based on configurations (org.eclipse.platform, org.eclipse.rcp and my own feature) and ran following command to generate the p2 profile:
eclipse -nosplash \
-application org.eclipse.equinox.p2.director.app.application \
-metadataRepository ${UPDATE_LOCATION} \
-artifactRepository ${UPDATE_LOCATION} \
-installIU com.sigasi.hdt.rcp.feature.feature.group \
-destination ${INSTALL_DIR} \
-profile HDTProfile \
-vmArgs \
with UPDATE_LOCATION the location of my P2 repository
and INSTALL_DIR the directory where my RCP was build

When I start an update inside my RCP, my plugin-jars are downloaded to the p2/org.eclipse.equinox.p2.touchpoint.eclipse/ plugins/ directory but not to the main plugins directory. So while the update UI displays that the feature is updated, the new plugins are not loaded because the old jars are still in the plugins directory.

How should I resolve this issue?

Kind regards,

p2-dev mailing list
p2-dev mailing list