|
|
| Re: how to exclude a feature from a p2 site ? [message #645044 is a reply to message #644685] |
Wed, 15 December 2010 10:38   |
 Stephane Bouchet
Messages: 280
Registered: July 2009 |
Senior Member |
|
|
peter,
thanks for your help, i can achieve what i wanted to do the following :
having a build feature that map the contains of my update site ( without
tests ) ( second tip you gave )
cheers,
Le 13/12/2010 19:52, Peter Nehrer a écrit :
> Did you try running site.p2 on your product feature after you've built
> your build feature? This should assemble the update site using
> features/plugins that you just built but without your test feature.
>
> Another alternative might be to remove your test feature from your build
> feature.xml and add it back in using buckminster.cspex. This way
> buckminster will see it for building purposes but it won't include it in
> the update site. E.g., here I exclude feature
> org.eclipse.equinox.executable from the update site:
>
> <cspecExtension
> xmlns:com="http://www.eclipse.org/buckminster/Common-1.0"
> xmlns="http://www.eclipse.org/buckminster/CSpec-1.0">
>
> <dependencies>
> <dependency name="org.eclipse.equinox.executable"
> componentType="eclipse.feature"/>
> </dependencies>
>
> <alterActions>
> <public name="buckminster.clean">
> <prerequisites>
> <attribute name="buckminster.clean"
> component="org.eclipse.equinox.executable"/>
> </prerequisites>
> </public>
> </alterActions>
>
> <alterGroups>
> <public name="bundle.jars">
> <attribute name="bundle.jars" component="org.eclipse.equinox.executable"/>
> </public>
> <public name="feature.references">
> <attribute name="feature.jars"
> component="org.eclipse.equinox.executable" contributor="false"/>
> </public>
> <public name="product.configuration.exports">
> <attribute name="product.configuration.exports"
> component="org.eclipse.equinox.executable"/>
> </public>
> <public name="source.bundle.jars">
> <attribute name="source.bundle.jars"
> component="org.eclipse.equinox.executable"/>
> </public>
> <public name="source.feature.references">
> <attribute name="source.feature.jars"
> component="org.eclipse.equinox.executable" contributor="false"/>
> </public>
> </alterGroups>
> </cspecExtension>
>
> --Peter
>
> On 12/13/10 11:58 AM, Stéphane Bouchet wrote:
>> hi,
>> i loooked around to find some directions to exclude a particular feature
>> from an update site produced by buckminster.
>>
>> i got a build feature that includes two feature, one for my update site
>> and one for the tests.
>>
>> But using that feature ends with a complete update site with tests
>> included.
>> How can i exclude the second feature ?
>>
>> note that i use hudson to build...
>>
>>
>>
>
--
Cheers,
Stéphane Bouchet, OBEO
|
|
|
| Re: how to exclude a feature from a p2 site ? [message #645079 is a reply to message #645044] |
Wed, 15 December 2010 14:10 |
Peter Nehrer
Messages: 241
Registered: July 2009 |
Senior Member |
|
|
I should have mentioned that #2 will actually include that feature in
your update site, but it won't be categorized and so won't show up as
top-level (in categorized view). Sorry about the confusion.
--Peter
On 12/15/10 5:38 AM, Stéphane Bouchet wrote:
> peter,
>
> thanks for your help, i can achieve what i wanted to do the following :
>
> having a build feature that map the contains of my update site ( without
> tests ) ( second tip you gave )
>
> cheers,
>
> Le 13/12/2010 19:52, Peter Nehrer a écrit :
>> Did you try running site.p2 on your product feature after you've built
>> your build feature? This should assemble the update site using
>> features/plugins that you just built but without your test feature.
>>
>> Another alternative might be to remove your test feature from your build
>> feature.xml and add it back in using buckminster.cspex. This way
>> buckminster will see it for building purposes but it won't include it in
>> the update site. E.g., here I exclude feature
>> org.eclipse.equinox.executable from the update site:
>>
>> <cspecExtension
>> xmlns:com="http://www.eclipse.org/buckminster/Common-1.0"
>> xmlns="http://www.eclipse.org/buckminster/CSpec-1.0">
>>
>> <dependencies>
>> <dependency name="org.eclipse.equinox.executable"
>> componentType="eclipse.feature"/>
>> </dependencies>
>>
>> <alterActions>
>> <public name="buckminster.clean">
>> <prerequisites>
>> <attribute name="buckminster.clean"
>> component="org.eclipse.equinox.executable"/>
>> </prerequisites>
>> </public>
>> </alterActions>
>>
>> <alterGroups>
>> <public name="bundle.jars">
>> <attribute name="bundle.jars"
>> component="org.eclipse.equinox.executable"/>
>> </public>
>> <public name="feature.references">
>> <attribute name="feature.jars"
>> component="org.eclipse.equinox.executable" contributor="false"/>
>> </public>
>> <public name="product.configuration.exports">
>> <attribute name="product.configuration.exports"
>> component="org.eclipse.equinox.executable"/>
>> </public>
>> <public name="source.bundle.jars">
>> <attribute name="source.bundle.jars"
>> component="org.eclipse.equinox.executable"/>
>> </public>
>> <public name="source.feature.references">
>> <attribute name="source.feature.jars"
>> component="org.eclipse.equinox.executable" contributor="false"/>
>> </public>
>> </alterGroups>
>> </cspecExtension>
>>
>> --Peter
>>
>> On 12/13/10 11:58 AM, Stéphane Bouchet wrote:
>>> hi,
>>> i loooked around to find some directions to exclude a particular feature
>>> from an update site produced by buckminster.
>>>
>>> i got a build feature that includes two feature, one for my update site
>>> and one for the tests.
>>>
>>> But using that feature ends with a complete update site with tests
>>> included.
>>> How can i exclude the second feature ?
>>>
>>> note that i use hudson to build...
>>>
>>>
>>>
>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03034 seconds
] 
Search
Help
Register
Login
Home
