Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Creating a Product and then updating via Update Site

Thanks for the information, Lars !

Do I understand right that when the bug 361722 is solved in Tycho, this will be a way to automate what is described here: ?

If so, then it's great. I have currently made appropriate changes to my build to do what is described in the blog post. But since it leads to lots of configuration in my product's pom.xml, as well as duplications of information (duplicating what's in the target platform for the root features repositories, for instance), I have currently only done that for 1 feature, my own plugin's feature. Far from ideal, then, because lots (if not all) of the other features included ( Eclipse default features, Eclipse colortheme, EGit, m2e, etc., etc. ) could use the same treatment.



2014/1/23 Lars Vogel <lars.vogel@xxxxxxxxx>
Hi Laurent,

AFAIK you want the feature what is hopefully delivered with the next Tycho release, install root level features into product install. 

Best regards, Lars

2014/1/18 Laurent PETIT <laurent.petit@xxxxxxxxx>
Hi Jeff,

2014/1/18 Jeff MAURY <jeffmaury@xxxxxxxxxxxxx>

is it still relevant ? I thought you've fixed it ?

Actually, I have since thursday been able to do a lot of trials and errors, thanks to the links, thanks to you ...

I haven't had the time to inform you, but I haven't been able to make the "intermediate product feature" solution work. 
Maybe I have misunderstood some explanation:

- I have created a ccw.product.feature feature, and now my ccw product includes only this feature in ccw.product
- I have a new tycho module for ccw.product.feature, and it basically declares all the features which were included directly in the product (Rcp, Application, JDT, CCW, EclipsecolorTheme, EGit, ...)

The Tycho builds a product, but I'm still unable to update eg CCW via the update site.

You were talking about a possible remaining issue with "root feature(s)" with this solution, I didn't at the time understand what you meant, maybe it's the missing piece ... ?


On Thu, Jan 16, 2014 at 10:49 PM, Laurent PETIT <laurent.petit@xxxxxxxxx> wrote:
Hi Paul, 

So thanks to you and the link, I've been able to fix my problem. I had to remove the ccw feature definition from the product features list, and instead add a to my product's ccw.p2.inf file.

And the final step is to manually invoke the Director to install to the product after the fact.

This is why I'm coming back to you. Since I've removed ccw.feature from the product features list, I don't find feature artifacts in my product's target/repository repository anymore. Before that, it was easy to point the Director to this directory.
So Ive pointed instead the directory to a relative path like ../ccw.updatesite/target/repository.

And it is working for ccw.feature, great !


I'd also like to make other features updatable independently by the user: egit, eclipse-colorthemes for instance.
And then starts the redundancy : I have already declared where to find these feature in my target definition, but I don't know how to reuse this.
Instead, I find myself repeating tycho-eclipserun-plugin calls, an for each call, pasting the location of external p2 repositories ...

There must be a better way with tycho, right ? I'm sure I'm not using it to its full potential ....

thanks in advance for any guidance,


2014/1/16 Laurent PETIT <laurent.petit@xxxxxxxxx>
Thank you both, Paul and Sandra, I will take a look at these links and try things ASAP.

2014/1/16 Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>
On Thu, Jan 16, 2014 at 8:48 AM, Laurent PETIT <laurent.petit@xxxxxxxxx> wrote:

There's something not working yet: once the product is installed, users are unable to update the counterclockwise plugin via the counterclockwise update site, meaning that they need to download and install a new version of the Product everytime they want to upgrade ..

See which has a section on upgrading components without upgrading the entire product.

If I'm reading it correctly, you need your product p2.inf to open up the ranges on the features the product include.


Paul Webster
Hi floor.  Make me a sammich! - GIR

tycho-user mailing list

tycho-user mailing list


"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

tycho-user mailing list

tycho-user mailing list

tycho-user mailing list

Back to the top