Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] why same feature qualifier for org.eclipse.sdk M1, M2a, M3?

Hi Nicloas,

Indeed. Y is greater then X so the versions go backwards. I think you should enter a bugzilla for this. It's rather serious given that everything is mixed in a composite.

- thomas

On 11/10/2010 11:48 AM, Nicolas Bros wrote:

I'm having dependency problems in the MoDisco Buckminster build for Indigo M3, and I'm searching why.
Buckminster materializes plug-ins both from M2a and M3, leading to conflicts.

I found this in the composite platform update site :


Why do all 3 features have the same date (20100629)?
Following the alphabetical order, 3.7M2a is last, so p2 would consider it the most recent I believe.

Nicolas Bros
tel: 06 75 09 19 88
Mia-Software, 410 clos de la Courtine
93160 Noisy-le-Grand
.: model driven agility :.

_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx

Back to the top