Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » P2 Director did not create features directory
P2 Director did not create features directory [message #126812] Mon, 02 March 2009 20:49 Go to next message
Eddie Galvez is currently offline Eddie GalvezFriend
Messages: 103
Registered: July 2009
Senior Member
Building a product using PDE headless build, allowing PDE to generate p2
metadata and publish artifacts. The result of the pde build
generated/published p2 repo looks like:


dist/PDEOUT/p2
|-- artifacts.xml
|-- binary
| `-- com.myproduct.launcher.gtk.linux.x86_6.4.0.qualifier
|-- content.xml
|-- features
| |-- com.myproduct_6.4.0.902271038.jar
| |-- org.eclipse.cvs_1.1.2.R342_v20090122-7C79E9x9sLM1t6M9YD7_A7. jar
| |-- org.eclipse.draw2d_3.4.2.v20090218-1145-3317w311_122502441.j ar
| |--
org.eclipse.equinox.p2.user.ui_1.0.2.r34x_v20090120-7d-7tEQc CaaYSBeNOClOn02267.jar
| |-- org.eclipse.gef_3.4.2.v20090218-1145-67728084A56B4I233613552 .jar
| |--
org.eclipse.help_1.0.2.R342_v20090122-7r7xEKaEJBZu5oGhP3u6nO mbM9VK.jar
| |--
org.eclipse.jdt_3.4.2.r342_v20081217-7o7tEAoEEDWEm5HTrKn-svO 4BbDI.jar
| |--
org.eclipse.platform_3.4.2.R342_v20090122-9I96EiWElHi8lheoJK JIvhM3JfVsYbRrgVIWL.jar
| `--
org.eclipse.rcp_3.4.200.R342_v20090122-989JESTEbig-SVaL8UJHc YBr4A63.jar
`-- plugins
|-- com.ibm.icu_3.8.1.v20080530.jar
|-- com.jcraft.jsch_0.1.37.v200803061811.jar
|-- com.myproduct.plugin1_6.4.0.902271038.jar
(etc)

Then, the directory is executed like this:

/eclipse342/eclipse -debug -consoleLog -nosplash --launcher.suppressErrors
-application org.eclipse.equinox.p2.director.app.application
-metadataRepository file:dist/PDEOUT/p2 -artifactRepository
file:dist/PDEOUT/p2 -installIU com.myproduct -destination P2TARGET
-profile MyProductProfile -profileProperties
org.eclipse.update.install.features=true -bundlepool P2TARGET -p2.os linux
-p2.ws gtk -p2.arch x86 -roaming -flavor tooling -vmargs
-Declipse.p2.data.area=P2TARGET/p2


but the result is:

P2TARGET/
|-- artifacts.xml
|-- p2
| |-- org.eclipse.equinox.p2.core
| | `-- cache
| | |-- artifacts.xml
| | `-- content.xml
| |-- org.eclipse.equinox.p2.director
| | `-- rollback
| | `-- content.xml
| `-- org.eclipse.equinox.p2.engine
| `-- profileRegistry
| |-- SDKProfile.profile
| | `-- 1236026322392.profile
| `-- MyProductProfile.profile
| |-- 1236026321886.profile
| `-- 1236026339881.profile
`-- plugins
|-- com.ibm.icu_3.8.1.v20080530.jar
(etc)


Missing "features" ! (I eventually learnt, not by the docs nor the wiki,
that the executable, ini file, etc are all in the "binary" zip)

En passant -- I picked a "profile" name at random... is that right?

Thank you,
Eddie
Re: P2 Director did not create features directory [message #126827 is a reply to message #126812] Mon, 02 March 2009 21:29 Go to previous messageGo to next message
Eddie Galvez is currently offline Eddie GalvezFriend
Messages: 103
Registered: July 2009
Senior Member
I want to follow up that I tried running the metadata generator by hand
based off of a non-p2 build output (what we have since we build our product
against 3.3), ran the director... and ended up with no features again! (Note
that the p2 repo created looks fine, features and plug-ins are present).

- Eddie
SOLVED - Re: P2 Director did not create features directory [message #126865 is a reply to message #126827] Mon, 02 March 2009 23:22 Go to previous message
Eddie Galvez is currently offline Eddie GalvezFriend
Messages: 103
Registered: July 2009
Senior Member
Huh, solved (pending runtime testing)

The documentation (scattered around wikis, newsgroups, etc.) should be clear
on something: the IU for a product should be the product ID used in the
extension point... I kept using "com.myproduct", which matches the primary
feature name. The product ID is "com.myproduct.product" and using that as an
installIU produced the right thing -- dropins folder even!

- Eddie

"Eddie Galvez" <eddie@grassybrook.com> wrote in message
news:gohj3e$sj3$1@build.eclipse.org...
>I want to follow up that I tried running the metadata generator by hand
>based off of a non-p2 build output (what we have since we build our product
>against 3.3), ran the director... and ended up with no features again!
>(Note that the p2 repo created looks fine, features and plug-ins are
>present).
>
> - Eddie
Previous Topic:secure storage preference ui features
Next Topic:Virtual bundles?!
Goto Forum:
  


Current Time: Thu Apr 25 07:04:26 GMT 2024

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

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

Back to the top