| Building and Installing an updateconfigurator-based product using p2 [message #68043] |
Mon, 13 July 2009 14:35 |
 Paul Warren
Messages: 34
Registered: July 2009 |
Member |
|
|
In the main we are building our server-side osgi applications to have a p2
capability and then managing these applications via p2. The build process
for this is obviously pretty standard - a pde-build, of a feature-based
product that includes p2 bundles, building with p2 metadata generation on,
followed by a p2 director install (as per Andrew N's suggestion). This is
working well.
But I also have a few consumers who are stuck on eclipse/equinox 3.3
technology for the time-being. Therefore they need a product image
configured with the updateconfigurator, rather than simpleconfigurator.
If possible I'd like to end up with a nice, simple & generic build process
for both sets of applications; i.e. I'd like both sets of applications to go
through the same build steps.
I've done some very simple tests where I tried to build a feature based
product that included updateconfigurator bundle only - no p2 bundles, no
simpleconfigurator.
It would appear that the result of the initial pde build produces the right
product image in that it has the right config.ini.
If I also generate p2 metadata & then perform the p2 install and then do a
p2 director this appears to produce a p2-ified image - in the sense that
simpleconfigurator gets added to the p2 repos and installed image's
config.ini gets re-written to use simpleconfigurator.
So, for updateconfigurator applications should I skip the p2 install OR is
there a way to get an updateconfigurator-based product image out of the p2
director install?
Many thanks
_Paul
P.S. Yes, yes we are trying to get them off updateconfigurator ASAP but in
the meantime I need to know how to automate the build their products
|
|
|
Powered by
FUDForum. Page generated in 0.02491 seconds
] 
Search
Help
Register
Login
Home
