| Making sub-components updateable via p2 [message #643475] |
Tue, 07 December 2010 01:33  |
 David Missing name
Messages: 11
Registered: December 2010 |
Junior Member |
|
|
Hello
I do apologise if this is not the right forum, I wasn't really sure which was the most appropriate.
The problem as stated here: http://aniefer.blogspot.com/2009/07/composing-and-updating-c ustom-eclipse.html. I'm not sure that the steps in this tutorial are applicable to our setup.
We need to add update functionality for sub-components of our product (which are all set as included features of the product), but p2 only checks for updates to the actual product and not the sub-components, it finds new software to install, but that obviously doesn't work.
We currently have our application being built using buckminster on hudson, following this tutorial, http://www.ralfebert.de/blog/eclipsercp/p2_updates_tutorial/ . Basically, we need to modify the build process to explicitly install each of our features (not including eclipse SDK, equinox, etc for now) so that those features are updateable via an update site. I am using eclipse 3.5, and buckminster 1.1.350.r11162 (in the IDE, I presume the version on the command line is the same).
The buckminster build flags in hudson are:
importtargetdefinition -A '${WORKSPACE}/site/rcp.target'
import '${WORKSPACE}/site/site.cquery'
build
perform -D target.os=win32 -D target.ws=win32 -D target.arch=x86 org.example.app.site#site.p2
perform -D target.os=win32 -D target.ws=win32 -D target.arch=x86 org.example.app.site#create.product.zip
David
[Updated on: Tue, 07 December 2010 01:47] Report message to a moderator |
|
|
| Re: Making sub-components updateable via p2 [message #643478 is a reply to message #643475] |
Tue, 07 December 2010 02:07  |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Create.product.zip calls create product which performs the installation
of the product.
What you probably want to do is to first install the base product, and
then install each individually updateable feature (which naturally can
not be included in the base product).
Once everything is installed, the result is zipped.
Look at the definition of create.product.zip
- henrik
<tran@acer.edu.au> wrote:
> Hello
>
> The problem as stated here:
> http://aniefer.blogspot.com/2009/07/composing-and-updating-c ustom-eclipse.html
> I'm not sure that the steps in this tutorial are applicable to our
> setup. We need to add update functionality for sub-components of our
> product (which are all set as included features of the product), but
> p2 only checks for updates to the actual product and not the
> sub-components, it finds new software to install, but that obviously
> doesn't work.
>
> We currently have our application being built using buckminster on
> hudson, following this tutorial,
> http://www.ralfebert.de/blog/eclipsercp/p2_updates_tutorial/
> Basically, we need to modify the build process to explicitly install
> each of our features (not including eclipse SDK, equinox, etc for now)
> so that those features are updateable via an update site. I am using
> eclipse 3.5, and buckminster 1.1.350.r11162 (in the IDE, I presume the
> version on the command line is the same).
>
> The buckminster build flags in hudson are:
>
> importtargetdefinition -A '${WORKSPACE}/site/rcp.target'
> import '${WORKSPACE}/site/site.cquery'
> build
> perform -D target.os=win32 -D target.ws=win32 -D target.arch=x86
> org.example.app.site#site.p2
> perform -D target.os=win32 -D target.ws=win32 -D target.arch=x86
> org.example.app.site#create.product.zip
>
>
> David
--
- henrik
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03518 seconds
] 
Search
Help
Register
Login
Home
