|
| Re: How to hide org.eclipse.equinox.executable? [message #534715 is a reply to message #534708] |
Thu, 20 May 2010 05:37   |
|
Don't include it in your site feature. Instead, add it as a dependency in your top level cspec. Alternatively add it as
a dependency in a cspex that resides in your site.feature.
HTH,
- thomas
On 05/20/2010 07:05 AM, Peter Nehrer wrote:
> Hi,
>
> I have a setup that is similar to the mail app tutorial, but I don't
> include org.eclipse.equinox.executable feature in my product feature --
> I include it in the site feature. This way I get the product
> configuration generated correctly (with all launcher dependencies) w/out
> "polluting" the product feature itself with the dependency.
>
> However, now the org.eclipse.equinox.executable feature shows up in the
> p2 repository (under "Uncategorized").
>
> Is there a way to hide it? I know I could hide the feature using p2.inf,
> but I don't own it -- it's in the target platform.
>
> Any ideas? Thanks.
>
> --Peter
|
|
|
| Re: How to hide org.eclipse.equinox.executable? [message #534939 is a reply to message #534715] |
Thu, 20 May 2010 17:35 |
 Peter Nehrer
Messages: 241
Registered: July 2009 |
Senior Member |
|
|
Thanks for the tip, Thomas. Unfortunately, it didn't quite do it -- it
behaved as if I didn't include the feature at all. The product IU was
created w/out links to the launchers. As a result, site.p2 was built
with no problems but I was unable to install any products from it:
Installing my.product 1.0.0.201005201243.
Cannot complete the install because one or more required items could not
be found.
Software being installed: My Product 1.0.0.201005201243 (my.product
1.0.0.201005201243)
Missing requirement for filter
(&(osgi.arch=x86_64)(osgi.os=macosx)(osgi.ws=cocoa)):
my.product.executable.cocoa.macosx.x86_64 1.0.0.201005201243 requires
'org.eclipse.equinox.launcher.cocoa.macosx.x86_64 0.0.0' but it could
not be found
Cannot satisfy dependency:
From: My Product 1.0.0.201005201243 (my.product 1.0.0.201005201243)
To: toolingmy.product.application [1.0.0.201005201243]
Cannot satisfy dependency:
From: toolingmy.product.application 1.0.0.201005201243
To: my.product.executable.cocoa.macosx.x86_64 [1.0.0.201005201243]
I ended up with the following cspex (after diffing the cspec of my site
feature with and without org.eclipse.equinox.executable included):
<?xml version="1.0" encoding="UTF-8"?>
<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>
Note that org.eclipse.equinox.executable's contribution is turned off in
feature.references and source.feature.references.
This seems to have done the trick.
I tried adding org.eclipse.equinox.executable to my site feature and
then removing it from feature.jars/source.feature.jars in cspex like this:
<alterGroups>
<public name="feature.references">
<alterAttribute name="feature.jars"
component="org.eclipse.equinox.executable" contributor="false" />
</public>
<public name="source.feature.references">
<alterAttribute name="source.feature.jars"
component="org.eclipse.equinox.executable" contributor="false" />
</public>
</alterGroups>
But this kept failing with ERROR CSpec my.site.feature, attribute
feature.references does not define prerequisite
org.eclipse.equinox.executable#feature.jars
Not sure if I used the right constructs, but the cspec (with
org.eclipse.equinox.executable included in feature.xml) does in fact
define that attribute. I'd still like to find out if this is possible --
it seems cleaner this way. Thanks!
--Peter
On 5/20/10 1:37 AM, Thomas Hallgren wrote:
> Don't include it in your site feature. Instead, add it as a dependency
> in your top level cspec. Alternatively add it as a dependency in a cspex
> that resides in your site.feature.
>
> HTH,
> - thomas
>
>
>
> On 05/20/2010 07:05 AM, Peter Nehrer wrote:
>> Hi,
>>
>> I have a setup that is similar to the mail app tutorial, but I don't
>> include org.eclipse.equinox.executable feature in my product feature --
>> I include it in the site feature. This way I get the product
>> configuration generated correctly (with all launcher dependencies) w/out
>> "polluting" the product feature itself with the dependency.
>>
>> However, now the org.eclipse.equinox.executable feature shows up in the
>> p2 repository (under "Uncategorized").
>>
>> Is there a way to hide it? I know I could hide the feature using p2.inf,
>> but I don't own it -- it's in the target platform.
>>
>> Any ideas? Thanks.
>>
>> --Peter
>
|
|
|
Powered by
FUDForum. Page generated in 0.02608 seconds
] 
Search
Help
Register
Login
Home
