| How to Build a product and update site with p2 metadata? [message #381639] |
Mon, 05 January 2009 20:45  |
Eclipse User |
|
|
|
Originally posted by: jconlon.apache.org
Hi,
I am trying to build a p2 enable RCP product, for multiple platforms
(linux and win) as well as a p2 repository to support it.
The end result would be 2 zip artifacts and an update site.
So far I have been able to build a product with Buckminster that runs
but, because it has no p3 metadata when I attempt to run Software
Updates I get an 'Cannot launch the Update UI' error dialog with the an
error log entry:
'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.'
Similarly when I build an update site based on a set of features
according to the 'Buckminster Building an Update Site' example it has no
p2 metadata.
To add metadata and a profile to the product, I found I could kludge
together a p2 enabled product by...
1. Creating a product with a buckminster generated cspec on the project
that contains my product.
2. Create a project and a cspec (Using Buckminster's Building an Update
Site' example) supplementing it with an ant action (Uses the p2 metadata
generator) that generates p2 metadata on the update site. Executing this
cspec action creates the updatesite and a p2 repo for the products features.
3. Create another project and a cspec to Run the P2 Metadata generator
on the Product build in #1 to generate a second metadata repository that
contains the launchable product metadata.
4. Run the p2 Director application pointing to the repo created in #3 to
install the executable product and creates a profile in the install
directory.
5. Run the p2 Director pointing to the repo created in #2 to install the
features into my directory.
In the directory created in 4 and updated in #5 I can start my
application and see that p2 is enabled. <Ugh/>
The above is pretty convoluted. Is there standard way in buckminster to
generate a product with p2 in one or two steps?
Does one need to create an update site before I create a repo?
How can I create a single p2 repo site and add to it both my feature UIs
and product UIs for the various platforms?
thanks for any help,
John
|
|
|
| Re: How to Build a product and update site with p2 metadata? [message #381640 is a reply to message #381639] |
Tue, 06 January 2009 11:51  |
|
Hi John,
The support for p2 in Buckminster is under way but not ready to be
released yet. Until it is, I'm afraid the kludge you've come up with is
as good as any. You must create an update site and then run the p2
generator on it. There no other way at present.
We're currently working hard together with the p2 team to resolve some
issues that currently prevents us from using p2 in a much larger scale
in Buckminster. I have good hopes that those issues will be resolved
fairly soon.
Kind regards,
Thomas Hallgren
John E. Conlon wrote:
> Hi,
>
> I am trying to build a p2 enable RCP product, for multiple platforms
> (linux and win) as well as a p2 repository to support it.
>
> The end result would be 2 zip artifacts and an update site.
>
>
> So far I have been able to build a product with Buckminster that runs
> but, because it has no p3 metadata when I attempt to run Software
> Updates I get an 'Cannot launch the Update UI' error dialog with the an
> error log entry:
> '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.'
>
>
> Similarly when I build an update site based on a set of features
> according to the 'Buckminster Building an Update Site' example it has no
> p2 metadata.
>
> To add metadata and a profile to the product, I found I could kludge
> together a p2 enabled product by...
>
> 1. Creating a product with a buckminster generated cspec on the project
> that contains my product.
>
> 2. Create a project and a cspec (Using Buckminster's Building an Update
> Site' example) supplementing it with an ant action (Uses the p2 metadata
> generator) that generates p2 metadata on the update site. Executing this
> cspec action creates the updatesite and a p2 repo for the products
> features.
>
> 3. Create another project and a cspec to Run the P2 Metadata generator
> on the Product build in #1 to generate a second metadata repository that
> contains the launchable product metadata.
>
> 4. Run the p2 Director application pointing to the repo created in #3 to
> install the executable product and creates a profile in the install
> directory.
>
> 5. Run the p2 Director pointing to the repo created in #2 to install the
> features into my directory.
>
> In the directory created in 4 and updated in #5 I can start my
> application and see that p2 is enabled. <Ugh/>
>
>
> The above is pretty convoluted. Is there standard way in buckminster to
> generate a product with p2 in one or two steps?
>
>
> Does one need to create an update site before I create a repo?
>
> How can I create a single p2 repo site and add to it both my feature UIs
> and product UIs for the various platforms?
>
> thanks for any help,
> John
>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03538 seconds
] 
Search
Help
Register
Login
Home
