c. Use the P2 Metadata Generator
For #2 you can do this from the p2 Repository you created in #1. Again I
think there are basically 3 ways to do this:
a. The P2 Installer
http://wiki.eclipse.org/Equinox_p2_Installer
b. The P2 Headless Director
http://wiki.eclipse.org/Equinox_p2_director_application
c. The P2 AdminUI (Haven't tried this way myself though I think it
should work.)
http://wiki.eclipse.org/Equinox_p2_Admin_UI_Users_Guide
Also see the previous 12/15/2008 news group message with subject
'Eclipse with P2'.
cheers,
John
Ben Vitale wrote:
When I run the Export wizard against a .product that has a dependency
on the org.eclipse.platform feature, I get all the p2 plugins included
in the export. I'm able to see the Software Updates menu item. But
clicking on it results in this message:
"Cannot launch the Update UI. This installation has not been
configured properly for Software Updates."
There is also this in the log:
!ENTRY org.eclipse.equinox.p2.ui.sdk 2 0 2009-01-07 10:01:12.549
!MESSAGE Could not locate the running profile instance. The
eclipse.p2.data.area and eclipse.p2.profile properties may not be set
correctly in this application's config.ini file.
Now I'm noticing that there is in fact no p2 data area in the exported
product output. I suspect the error I'm seeing is the one referenced
in this bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=221513
Is there a flag that should be set on the build.properties file to
trigger the generation of p2 metadata?
Thanks
Ben