Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Build product and then install with Tycho

Whatever workaround you do, make sure you also watch for explicit support by Tycho for this use case.






From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Jason Litton
Sent: Freitag, 26. April 2013 00:07
To: Tycho user list
Subject: [tycho-user] Build product and then install with Tycho


Hi all,

I'm new to release and build engineering, and I'm trying to get our Eclipse builds off of pde and onto Tycho. But I'm getting blocked here. I was hoping I could describe our build workflow and see if there's anyone doing something similar and could give me some tips. I feel like I'm 90% there, but I can't find any examples or documentation that points the way.



1) Build all features and plugins <- this is fine with Tycho

2) Build a p2 update site <- also fine

3) Build a minimal Eclipse product (platform and help) with an executable <- also fine

4) Install the features from the p2 update site in step 2 into the product built in step 3 <- we do this so we can update those features later, I have no idea how to do this!


I've tried using the eclipse-run-plugin according to the example here:

But that doesn't give me an installation. If I include my features into my product definition and use the eclipe-repository type packaging, then those features can't be updated. Is there anyone else who is working this way? If so, can you point me towards an example or something that shows this kind of workflow? I've scoured google, and seen all the typical examples, but I don't see anyone doing it quite this way in them. If this is the wrong way to go, could I get some tips on setting up a product definition that includes features in a way that they CAN be updated?


Thanks a lot,

Jason Litton

Back to the top