Installing third party features [message #662680] |
Thu, 31 March 2011 10:37  |
Eclipse User |
|
|
|
Hello,
In the product that we build we have a dependency on third party features. Currently these features are part of target platform and make it into product as such. I am looking at changing this process. In my first approach I removed third party features from target platform and added entry to rmap using searchPath of readerType p2 that reference update site - this works. The reason we want to do this is because third party features change quite a bit and this will free us from rebuilding target platform every time there are incoming changes. Also, they don't have their own update site (yeah I know weird), that's why we are creating update site from their plugins.
Another approach I want to try is to remove dependency on third party features from product and install them manually, but I am not quite sure how to do that. Can someone suggest how should I go about doing this? Also, is this a good approach or having dependency on the feature with rmap realization is better solution?
thanks,
Alex
[Updated on: Thu, 31 March 2011 11:03] by Moderator
|
|
|
Re: Installing third party features [message #662755 is a reply to message #662680] |
Thu, 31 March 2011 15:39   |
Eclipse User |
|
|
|
When you say you "want to install them manually" - do you mean that the
user of your product should install them manually after they installed
your product?
If so, then you can have a site feature that includes the 3d party
features/bundles, but your product does not depend on these. When you
create the product it will naturally not include them. They are however
found in the same repository (you need to include the p2 UI in your
product to allow the user to perform installs and updates - or provide
your own ui).
It is also possible to compose the p2 repositories using a composite
repository - you may want a single point of entry for the user
install/updates and modify this repository between releases. You could
for instance have a 3d party repository that your overall/official
repository is referencing together with a reference to the things you
build. How to organize this is a matter of size/complexity/frequency of
change and taste :)
- henrik
On 3/31/11 4:37 PM, Alex Kravets wrote:
> Hello,
>
> First of all my user name has changed to Alex Kravets from Alex. I find
> it weird that two people can have the same user name - at least the
> display user name, like this user and myself:
> http://www.eclipse.org/forums/index.php?t=msg&th=206872& amp;start=0&S=07e7ebbef0e7fe4427b6b9a80e2005d6,
> isn't forum application need to check for duplicate user names?
>
> And now with my question....
>
> In the product that we build we have a dependency on third party
> features. Currently these features are part of target platform and make
> it into product as such. I am looking at changing this process. In my
> first approach I removed third party features from target platform and
> added entry to rmap using searchPath of readerType p2 that reference
> update site - this works. The reason we want to do this is because third
> party features change quite a bit and this will free us from rebuilding
> target platform every time there are incoming changes. Also, they don't
> have their own update site (yeah I know weird), that's why we are
> creating update site from their plugins.
>
> Another approach I want to try is to remove dependency on third party
> features from product and install them manually, but I am not quite sure
> how to do that. Can someone suggest how should I go about doing this?
> Also, is this a good approach or having dependency on the feature with
> rmap realization is better solution?
>
> thanks,
> Alex
|
|
|
|
Re: Installing third party features [message #664420 is a reply to message #664357] |
Fri, 08 April 2011 14:03  |
Eclipse User |
|
|
|
On 4/8/11 4:22 PM, Alex Kravets wrote:
> Quote:
>> When you say you "want to install them manually" - do you mean that
>> the user of your product should install them manually after they
>> installed your product?
>
>
> Bad choice of word "manually". I want to install features from another
> p2 site into my product during build process.
>
You can present several repositories to the director that produces the
installable application (to be zipped), or use aggregation/composition
to compose a single repository containing everything you need in present
for the install to work.
- henrik
|
|
|
Powered by
FUDForum. Page generated in 0.05089 seconds