Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » p2 FeaturesAndBundlesPublisher
p2 FeaturesAndBundlesPublisher [message #484770] Wed, 09 September 2009 08:07 Go to next message
Wieant is currently offline WieantFriend
Messages: 8
Registered: July 2009
Junior Member
We are in the process of switching from Ganymede to Galileo, and in that process would like to add
p2 support. We have our own build process that creates a perfectly running eclipse tree, that is,
without (p2) update support. If I understand correctly we have to generate p2 metadata and on the p2
wiki http://wiki.eclipse.org/Equinox/p2/Publisher found the following headless application call to
do this:
java -jar eclipse/plugins/org.eclipse.equinox.launcher_1.0.200.v200905 20.jar -application
org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher -metadataRepository file:/loc/p2
-artifactRepository file:/loc/p2 -source eclipse -configs gtk.linux.x86 -compress -publishArtifacts

In this case the command is run from the directory containing the 'eclipse' directory. Unfortunately
the application exits with exit code 13 but without generating any kind of error message? So if
someone sees the obvious we're doing wrong please let us know.

Regards,
Wieant
Re: p2 FeaturesAndBundlesPublisher [message #484794 is a reply to message #484770] Wed, 09 September 2009 10:43 Go to previous messageGo to next message
Wieant is currently offline WieantFriend
Messages: 8
Registered: July 2009
Junior Member
> We are in the process of switching from Ganymede to Galileo, and in that
> process would like to add p2 support. We have our own build process that
> creates a perfectly running eclipse tree, that is, without (p2) update
> support. If I understand correctly we have to generate p2 metadata and
> on the p2 wiki http://wiki.eclipse.org/Equinox/p2/Publisher found the
> following headless application call to do this:
> java -jar
> eclipse/plugins/org.eclipse.equinox.launcher_1.0.200.v200905 20.jar
> -application
> org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher
> -metadataRepository file:/loc/p2 -artifactRepository file:/loc/p2
> -source eclipse -configs gtk.linux.x86 -compress -publishArtifacts
>
> In this case the command is run from the directory containing the
> 'eclipse' directory. Unfortunately the application exits with exit code
> 13 but without generating any kind of error message? So if someone sees
> the obvious we're doing wrong please let us know.

I've made some progress, first found out to set -Dosgi.debug=.debug, which showed
the configuration area for the eclipse I'm trying to generate p2 metadata for, and in
its 'config' subdirectory a .log file was generated with the actual error message:
java.lang.RuntimeException: Application
org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher " could not be found in the registry.
To be continued...
Re: p2 FeaturesAndBundlesPublisher [message #484853 is a reply to message #484794] Wed, 09 September 2009 14:00 Go to previous messageGo to next message
Paul Webster is currently offline Paul WebsterFriend
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

While debugging an application, you can add a -consoleLog to the arguments and it will print out any errors to the console.

Also, are you running against the full eclipse SDK (which works) or against your RCP app that was exported in an eclipse directory (which won't work)?

I ran your command against a 3.5 install and it worked. You need to run it from your 3.5 install and use your RCP app as your source directory

PW


Re: p2 FeaturesAndBundlesPublisher [message #484865 is a reply to message #484853] Wed, 09 September 2009 14:17 Go to previous message
Wieant is currently offline WieantFriend
Messages: 8
Registered: July 2009
Junior Member
> While debugging an application, you can add a -consoleLog to the
> arguments and it will print out any errors to the console.
>
> Also, are you running against the full eclipse SDK (which works) or
> against your RCP app that was exported in an eclipse directory (which
> won't work)?
>
> I ran your command against a 3.5 install and it worked. You need to run
> it from your 3.5 install and use your RCP app as your source directory

I ran it against our Eclipse product, problem was that that didn't contain all the required p2 stuff
yet. After adding that the command seems to work correctly. Thanks also for the -consoleLog hint.

-- Wieant
Previous Topic:IProgressMonitor: progress is not shown in statusLine
Next Topic:Problem with keybinding context
Goto Forum:
  


Current Time: Thu Apr 25 12:36:23 GMT 2024

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

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

Back to the top