Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Inconsistency in the Platform's Mars Milestones Update Site

Oh sure ... blame releng when the metadata is bad. :)

I have opened
Bug 462851 - wrong value used for osgi.arch for ppc64le

and see

Bug 461427 - SWT fragment missing on classpath

for some of the (long) history of how SWT's meta data ended up this way.

From:        Ed Merks <ed.merks@xxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        03/23/2015 10:05 AM
Subject:        [cross-project-issues-dev] Inconsistency in the Platform's Mars        Milestones Update Site
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx


It looks like the p2 metadata in for SWT is questionable as of December 10th, 2014.  In particular the SWT IU now has more requirements than it had before:

I suppose that isn't in and of itself a problem (though I wonder why), but note in particular that the requirement for org.eclipse.swt.gtk.linux.ppcle64 is inconsistent with respect the actual IUs provided:

I.e., specifically note that the requirement ends with le64 but the actual available IU ends with 64le.

This causes problems for Oomph when the targlet infrastructure tries to resolve a target platform that includes all platforms (as is the case for JDT's Oomph setup and is that way because JDT itself provides platform-specific fragments). 

No doubt this is something that needs the attention of the platform's Releng team...

cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top