Skip to main content

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

Hi,

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 :

S-3.7M1-201008051700/features/org.eclipse.sdk_3.7.0.v20100629-7Q7t-DPY2lXAsz0ngujjWy0i17bPiZUwAz0A8mqupM3lG.jar
S-3.7M2a-201009211024/features/org.eclipse.sdk_3.7.0.v20100629-7Q7t-DPY2mYAyjigmrpYEb4Q44gPf5Y-94Wa22bALqtMJ.jar
S-3.7M3-201010281441/features/org.eclipse.sdk_3.7.0.v20100629-7Q7t-DPX2naDL1jfutmm2idmoY-eH81sz-yIoQxy-Yeup.jar

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
R&D
tel: 06 75 09 19 88
nbros@xxxxxxxxxxxxxxxx
nbros.mia@xxxxxxxxx
Mia-Software, 410 clos de la Courtine
93160 Noisy-le-Grand
http://www.mia-software.com
.: model driven agility :.


Back to the top