[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] exporting the dependencies of a feature
- From: Jacek Pospychała <jacek.pospychala@xxxxxxxxx>
- Date: Tue, 21 Dec 2010 13:36:08 +0100
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=xgB3qtuLOzGrLT1XYiu4xbff4BiOYOm0fHLmdev3aENlgQuSCrFcvRyoPa3Dz+4Ufe 8xXZJGcByrOFPRrSBST3aYfMkhrXq7h326VZqRsNfWQn2UjnpSIGHetQ+dpihM9rrN8j K1qeDQ5bTRsgSRGD7hubYHOwny8z0gyDbNWfM=
Good question... I'd like to learn the answer as well.
I'm trying to build repo of a feature built with PDEBuild. So I'm adding p2.gathering=true in build.properties. This produces repository in BuildDirectory\buildRepo, but it contains more than the feature and inclusions. So not exactly what I want.
On the other hand, using p2.publish.featuresAndBundles task ends with repository without inclusions - same as for Radu.
On Tue, Dec 21, 2010 at 9:59 AM, <radu.kopetz@xxxxxxxxxxxxxxxxxx>
I am trying to use the Publisher API described here
to export a feature.
Everything works fine: the metadata is correctly created and the binary
of the feature is present in the created "features" folder. The only
problem is that the plugins contained in the feature are not published.
Do I need to set a flag somewhere in order to export everything
contained in the feature (included plugins, features, etc) ?
Thanks in advance for your help !
p2-dev mailing list