|Re: Providing subset of site.p2 [message #675836 is a reply to message #675539]
||Wed, 01 June 2011 15:47
| Carsten Reckord
Registered: July 2009
Why do you want a subset without the RCP parts at all? Why not have a site
that includes the product feature and executables, too? Without them, you'll
most likely run into rather ugly dependency violations if you ever want to
use p2 to update your product.
What we do in our product build is
- include the RCP feature in our site feature, so the site contains everything
- make the RCP feature's "product" action use the prebuilt site instead of
building one on its own
On 31.05.2011 17:21, Miles Parker wrote:
> For one of my builds, I'd like to provide:
> 1) A complete RCP product build
> 2) A p2 update site that includes a plugin version of the product.
> 3) Eventually, an update site (or a packaging of 2) for the RCP build.
> 1 and 2 of course overlap significantly but they are disjoint. Naturally, I've setup my build for a feature that contains the the union of features for both. The RCP build is fine of course, and only includes the bits that I want. But the P2 site contains all of the artifacts for the RCP build including even some Eclipse components. Even if I limit the category.xml to the Eclipse plugin features, the RCP and Eclipse bits show up under "Uncategorized". Is there an integrated way to produce a subset update site for just 2) from the same build, or do I have to set up a separate job and cspec for it?
Visit our website, follow us on twitter and become a fan on facebook!
t +49 (0)561 5743277-33
f +49 (0)561 5743277-8833
Yatta Solutions GmbH
Sitz der Gesellschaft: Kassel
Amtsgericht Kassel, HRB 14720
Dr. Christian Schneider
t +49 (0)561 5743277-0
f +49 (0)561 5743277-88
Kasseler Bank eG
BLZ 520 900 00
Kto-Nr 158 305
Powered by FUDForum
. Page generated in 0.01590 seconds