RE: [cross-project-issues-dev] RE: [HeliosAggregation] Failed forbuild 2

[Andrew Niefer <aniefer@xxxxxxxxxx>]

PDE/Build and p2 support arbitrary LDAP filters on feature entries since 3.6M7 :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=293715

There is no UI for this, but you can edit the feature.xml and add a "filter" attribute manually.

<plugin id="o.e.tm.terminal.local" version="1.2.3" filter="(!(osgi.os=win32)" />

Note the p2 support here is on the metadata publishing side. Consuming the resulting metadata works fine in earlier releases.

-Andrew

"Oberhuber, Martin" ---05/31/2010 03:47:14 PM---> where bundle filters can not be more stringent that feature filters (if I'm saying that right :).

From:	"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
To:	"Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>
Date:	05/31/2010 03:47 PM
Subject:	RE: [cross-project-issues-dev] RE: [HeliosAggregation] Failed forbuild 2010-05-31_13-25-07
Sent by:	cross-project-issues-dev-bounces@xxxxxxxxxxx

---

> 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 somehow
   https://bugs.eclipse.org/bugs/show_bug.cgi?id=312011 
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
https://bugs.eclipse.org/bugs/show_bug.cgi?id=314977 and its predecessor.
 
If I remove the bundle filter, people install something that does not work.... see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=314193
 
At the moment, we are struggling with Athena CBI getting to build / test another feature that is Windows Only
https://bugs.eclipse.org/bugs/show_bug.cgi?id=315059
 
Oh my, how I love release engineering.
 
For now, I'm going to remove the tm.terminal.local contribution from Helios. Until any of the 4 bugs 
mentioned can be fixed.
 
Thanks,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
direct +43.662.457915.85  fax +43.662.457915.6

---

From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Monday, May 31, 2010 8:09 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] RE: [HeliosAggregation] Failed forbuild 2010-05-31_13-25-07


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. 

Thanks,

From:	"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
To:	David M Williams/Raleigh/IBM@IBMUS, <cross-project-issues-dev@xxxxxxxxxxx>
Date:	05/31/2010 01:49 PM
Subject:	[cross-project-issues-dev] RE: [HeliosAggregation] Failed for build 2010-05-31_13-25-07
Sent by:	cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Hi David, 
  
all I can say is that this feature (and its included plug-in) correctly exist in our contributing repository, 
http://download.eclipse.org/dsdp/tm/updates/3.2milestones 
  
I have 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 an
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 +43.662.457915.6

---

From: David M Williams [mailto:david_williams@xxxxxxxxxx] 
Sent: Monday, May 31, 2010 7:37 PM
To: cross-project-issues-dev@xxxxxxxxxxx
Cc: David Dykstal; Oberhuber, Martin
Subject: Re: [HeliosAggregation] Failed for build 2010-05-31_13-25-07


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 repo? 

Thanks,

From:	David M Williams/Raleigh/IBM@IBMUS
To:	David Dykstal <dykstal@xxxxxxx>, Martin Oberhuber <martin.oberhuber@xxxxxxxxxxxxx>
Cc:	David M Williams/Raleigh/IBM@IBMUS
Date:	05/31/2010 01:28 PM
Subject:	[HeliosAggregation] Failed for build 2010-05-31_13-25-07

---

The following errors occured when building Helios:

Software being installed: all.contributed.content.feature.group 1.0.0

Missing requirement: org.eclipse.tm.terminal.local.feature.group 0.1.0.v201005290650-41A78y8DfD-IAN8IB883222 requires 'org.eclipse.tm.terminal.local [0.1.0.v201005281600]' but it could not be found

Cannot satisfy dependency: all.contributed.content.feature.group 1.0.0 depends on: org.eclipse.tm.terminal.local.feature.group 0.1.0.v201005290650-41A78y8DfD-IAN8IB883222

Check the log file for more information: https://build.eclipse.org/hudson/view/Repository%20Aggregation/job/helios.runAggregator/116/console


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev