[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Is it possible to install a feature into an RCP app at build time?
- From: Trace Windham <twindham@xxxxxxxxx>
- Date: Wed, 16 May 2012 14:18:18 -0500
- Delivered-to: firstname.lastname@example.org
First off, thank you for all of your help, I'm learning a great deal today.
The good news is that I have something that works now.
The bad news is that it is not quite working as desired.
By making the modifications that you suggested to my <<product-id>>.p2.inf file, I have successfully had my feature installed into my RCP application. Unfortunately, it is not installed at the root level of installed features. Instead, the feature is a child of the main RCP feature of my RCP application, and therefore when updates are available for this child feature they are not found during the execution of the "Check For Updates" command in my RCP application. My requirement is that this feature be independently updatable without having to be manually installed by a user. I think this is what the patch in bug 361722 addresses.
Do you think I'm accurate in this explanation? I'm not yet confident of my knowledge in this area.
On Wed, May 16, 2012 at 1:34 PM, Brian de Alwis <briandealwis@xxxxxxxxx>
> <?xml version="1.0" encoding="UTF-8"?>You can simplify these for Tycho and just specify the id attribute; that'll cause Tycho to pick up the latest version. I doubt Tycho even uses the url attribute.
> <feature url="" id="com.mydomain.myrcpapp.rcp.feature" version="1.1.7.qualifier">
> <category name="com.mydomain"/>
Tycho will find it as long as the feature is available in either your ~/.m2/repository, one of the configured <repository/>, or is one of the projects being built.
> How is the RCP build going to find that? My other feature is built completely independently of the RCP build. When I ran my RCP build, the other feature still was not pre installed.
Ah, that's likely the problem: the repository has to be added to your list. You should be able to add something like the following to your pom.xml:
> So I modified the RCP's category.xml by adding the url of my other feature's p2 repository and made it look like this,
> <feature url="" href="http://mydomain.com/p2reposiotry/myotherfeature/features/com.mydomain.myotherfeature.feature_1.0.0.qualifier.jar" target="_blank">http://mydomain.com/p2reposiotry/myotherfeature/features/com.mydomain.myotherfeature.feature_1.0.0.qualifier.jar" id="com.mydomain.myotherfeature.feature" version="1.0.0.qualifier">
> But, that didn't work either.
(note that there appears to be a typo: "reposiotory" vs "repository")
Well I do it in my product builds and have been for over a year ;)
p2-dev mailing list