RE: [cross-project-issues-dev] RE: [HeliosAggregation] Failed forbuild 2010-05-31_13-25-07
> where bundle filters can not
be more stringent that feature filters (if I'm saying that right :).
Bummer. Yes, that's our case ... bundle filter is more
stringent than feature filter.
I thought that I do monitor cross-project bugs, but
slipped my attention. Or I just didn't understand that
this applies to me.
Problem is, if I add a feature filter I cannot build
the feature anymore (many thanks, PDE build).... see
If I remove the bundle filter, people install something
that does not work.... see
At the moment, we are struggling with Athena CBI
getting to build / test another feature that is Windows Only
Oh my, how I love release
For now, I'm going to remove the tm.terminal.local
contribution from Helios. Until any of the 4 bugs
mentioned can be fixed.
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
+43.662.457915.85 fax +43.662.457915.6
Ok, thanks. You might check if any of the discussion in
bug 312011 applies to you ... https://bugs.eclipse.org/bugs/show_bug.cgi?id=312011
where bundle filters can not be more
stringent that feature filters (if I'm saying that right :).
But, yes, if that bugzilla
discussion doesn't cover this case, please open a new one in cross-project list.
||David M Williams/Raleigh/IBM@IBMUS,
||05/31/2010 01:49 PM
[HeliosAggregation] Failed for build
Hi David, all I can say is
that this feature (and its included plug-in) correctly exist in our contributing
installed this feature multiple times today on multiple different hosts, and not
found any issues. I have
double-and triple-checked the qualifiers, and they are good. The only "special"
thing about the o.e.tm.terminal.local bundle is that its MANIFEST.MF has
Eclipse-PlatformFilter: (!(osgi.os=win32)) which
makes it not installable on Windows - not unlike what the Linuxtools
contribution does. During the RC3 cycle, I had made multiple experiments with
adding a platform filter to the o.e.tm.terminal.local-feature as well. And, my repository's site.xml does
also have a related platform
filter. But again, the current configuration is valid. This must be a bug
in the aggregator. I suggest tracking it in Bugzilla. Thanks,
-- Martin Oberhuber, Senior Member of Technical Staff,
Wind River direct +43.662.457915.85 fax
From: David M Williams [mailto:david_williams@xxxxxxxxxx]
Sent: Monday, May 31, 2010 7:37 PM
Cc: David Dykstal; Oberhuber,
Subject: Re: [HeliosAggregation] Failed for build
Martin and I have exchanged some brief notes about this last night
... this is the reason I temporarily removed some dsdp-tm features.
So, Martin, I think I've
correct restored everything now, and will assume you'll investigate, and let us
know if its a "builder mystery" or if you do find something missing from your
||David Dykstal <dykstal@xxxxxxx>,
Martin Oberhuber <martin.oberhuber@xxxxxxxxxxxxx>
||05/31/2010 01:28 PM
||[HeliosAggregation] Failed for build
The following errors occured
when building Helios:
Software being installed:
'org.eclipse.tm.terminal.local [0.1.0.v201005281600]' but it could not be
Cannot satisfy dependency: all.contributed.content.feature.group
1.0.0 depends on: org.eclipse.tm.terminal.local.feature.group
Check the log file for more