Eclipse Community Forums: Equinox » Using P2 within an feature based rcp application

Help

Home

Home » Eclipse Projects » Equinox » Using P2 within an feature based rcp application

Show: Today's Messages :: Show Polls :: Message Navigator

Using P2 within an feature based rcp application [message #112796]

Fri, 27 June 2008 17:40

Rich Scott

Messages: 63
Registered: July 2009

Member

I've been looking at moving our RCP application from use of the update
manager to p2 for installation and update and have made a lot of progress
the last 2 days. This is in no small part due to Kai Tödter's and Andrew
Niefer's posts, and all of the bug fixes in the final 3.4 release.

The application has a product configuration based upon features. I have
been able to export the product with metadata using the PDE UI. An can
now use p2Installer to install from the repository that was created. The
installed application works fine, but I have noticed that their is no
longer a features directory. Is that the way that you expect a p2 based
install to operate?

My target platform for the development is the RCP-SDK binary. So I had
manually identify all of the plugins required for p2 and add them to the
target environment. Is there a way to quickly produce that list?

One item that I ran across may help others going down this path. It had me
stumped for a while. I changed to provided p2Installer properties file to
include data about my application. When I ran the install, it would
quietly end without doing anything. The problem turned out to be the way
I specified the repository in the install.properties file. My initial try
had:

eclipse.p2.metadata=file:D:\eclipse.build\repository
eclipse.p2.artifacts=file:D:\eclipse.build\repository

IT turns out that the '\' in that file have to be escaped or replaced by
'/'.

So magic required to fix that problem was changing to

eclipse.p2.metadata=file:D:/eclipse.build/repository
eclipse.p2.artifacts=file:D:/eclipse.build/repository

Thanks
Rich

Report message to a moderator

Re: Using P2 within an feature based rcp application [message #113013 is a reply to message #112796]

Mon, 30 June 2008 14:58

Rich Scott

Messages: 63
Registered: July 2009

Member

After additional investigation, I found that the p2 director application
has the "-profileProperties org.eclipse.update.install.features=true"
option. So I tried using director instead of the p2installer to handle
generation of the p2 enabled install. With the director I now get the
features directory generated and populated. However, non of the feature
branding appears in the about dialogs. The change in the about dialog
appears to be the result of the changes made to config.ini by the director
as the install is done.

What needs to be done to enable feature details presented in the about
dialog while p2 updating is also enabled?

It appears that this is possible since the RCP developer distribution of
eclipse is p2 enabled and has extensive feature detail information
presented in the about dialog.

Thanks for any help

Report message to a moderator

Re: Using P2 within an feature based rcp application [message #113571 is a reply to message #113013]

Wed, 09 July 2008 02:47

Pascal Rapicault

Messages: 333
Registered: July 2009
Location: Ottawa

Senior Member

p2 does not register the necessary services (IBundleGroup) to be able to
have this information being displayed.
It is working in the SDK because update manager that is still around does
the work of registering the services.
This is something we would like to address in 3.5.

"Rich Scott" <rscott@cas.org> wrote in message
news:ad8fb01163d7fa73947e5263ea1d14f4$1@www.eclipse.org...
> After additional investigation, I found that the p2 director application
> has the "-profileProperties org.eclipse.update.install.features=true"
> option. So I tried using director instead of the p2installer to handle
> generation of the p2 enabled install. With the director I now get the
> features directory generated and populated. However, non of the feature
> branding appears in the about dialogs. The change in the about dialog
> appears to be the result of the changes made to config.ini by the director
> as the install is done.
> What needs to be done to enable feature details presented in the about
> dialog while p2 updating is also enabled?
> It appears that this is possible since the RCP developer distribution of
> eclipse is p2 enabled and has extensive feature detail information
> presented in the about dialog.
>
> Thanks for any help
>
>
>

Report message to a moderator

Previous Topic:	Documentation for Eclipse Applications
Next Topic:	p2: generate metadata over networked drive

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 19:35:46 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter