Blog

This Post Has 12 Comments

1. Alexander October 15, 2010 Reply

   This one will help
   dev.eclipse.org/mhonarc/lists/p2-dev/msg03225.html

2. Kai Tödter October 15, 2010 Reply

   @Alexander, thanks a lot, but I think msg03225.html addresses another issue. All of the above bundles are in the target platform. If I remove the feature org.eclipse.equinox.p2.user.ui from the product, I still get very similar errors.

3. Alb October 15, 2010 Reply

   I’ve been trying all week to get headless updating working with Helios, it’s a nightmare. A couple of days ago I posted to the dev list with where I’m now stuck (http://dev.eclipse.org/mhonarc/lists/p2-dev/msg03448.html). I can’t find any complete idiot proof example that works with Helios. At this point, I feel like the idiot that needs one though!

4. Alb October 15, 2010 Reply

   @Alb Also I’ve posted my problem on stack overflow: http://stackoverflow.com/questions/3944953/error-during-p2-eclipse-rcp-app-headless-update It would be great to get a definitive code-snippet for headless updating in Helios.

5. Frode October 16, 2010 Reply

   Yes, I have a working pde headless build for a rather large RCP application (product build, composite repository mirroring with JarComparator checking, Junit4 tests). Migration to 3.61 from 3.5.1 was painful.

   I had issues similar to what you are seeing. Mine was related to target platform and p2 insisting on pulling in optional dependencies. I.e. making optional references non optional. My workaround was removing all p2 metadata from target platform ( I now have a simple tp/eclipse/plugins and tp/eclipse/features structure). I guess I should try to regenerate the metadata, but I have not gotten around to this yet.

   I had two more issues:

   1) Including org.apache.ant disabled my junit4 tests

   2) p2 mirroring of org.eclipse.rcp feature with JarComaprator failed for binary identical feature jars. See bug: 327822

6. Kai Tödter October 16, 2010 Reply

   @Alb @Frode @Alexander

   Thank you very much guys! With your combined help I could get RCP p2 update working again and also successfully run the PDE build with 3.6.1. I’ll will blog about the solutions in a separate blog post soon.

7. Pingback: Kai's Blog » Eclipse RCP p2 self-update with Eclipse 3.6.1

8. Pingback: Kai's Blog » Eclipse RCP 3.6.x: Got Headless PDE Build working

9. Ponyno November 10, 2010 Reply

   Hi,

   My PDEBuild for a product (not RCP, just pure OSGi) work fine on windows. When I try to run it on Linux (RedHat 64bits), the target p2.director tells me like you. It is a nightmare how PDEBuild works sometimes and does not work sometimes…
   Could you help me please ?!

   Ponyno.

   [p2.director] Installation failed.
   [p2.director] An error occurred while collecting items to be installed
   [p2.director] session context was:(profile=profile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
   [p2.director] No repository found containing: osgi.bundle,org.apache.ant,1.7.1.v20100518-1145
   [p2.director] No repository found containing: osgi.bundle,org.eclipse.ant.core,3.2.200.v20100427
   [p2.director] No repository found containing: osgi.bundle,org.eclipse.core.runtime.compatibility.auth,3.2.200.v20100517
   [p2.director] An error occurred while collecting items to be installed
   [p2.director] session context was:(profile=profile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
   [p2.director] No repository found containing: osgi.bundle,org.apache.ant,1.7.1.v20100518-1145
   [p2.director] No repository found containing: osgi.bundle,org.eclipse.ant.core,3.2.200.v20100427
   [p2.director] No repository found containing: osgi.bundle,org.eclipse.core.runtime.compatibility.auth,3.2.200.v20100517
   A problem occured while invoking the director.

10. Fredrik Attebrant February 8, 2011 Reply

    Hi,

    Have you revisited this?
    According to bug 327706 it is fixed in both the 3.7 stream and also for 3.6.2.
    I downloaded 3.6.2 RC2 and gave it a try, since we ran into this with 3.6 for our RCP product.
    It works fine now, except when I try to export for multiple platforms, where I get an error about missing the launcher for the “cross platforms”..

    “Processing inclusion from feature org.eclipse.equinox.executable: Unable to find plug-in: org.eclipse.equinox.launcher.win32.win32.x86_1.1.2.R36x_v20101222. Please check the error log for more details.” (No more details to be found in the log…)

    Just checking to see if you’ve tried this?

    Thanks,
    –Fredrik

11. Fredrik Attebrant February 9, 2011 Reply

    Problem solved.
    Had first forgotten to configure the target platform with the delta pack for 362RC2 and then
    also for macosx, a launcher name must be explicitly entered on the “Launching” tab in the product config editor.
    Now headless builds works just fine!
    Sweet.

12. Kai Tödter February 28, 2011 Reply

    this is fixed with 3.6.2