Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326764

Summary:	Order of included features influences build success
Product:	z_Archived	Reporter:	Michael Wenz <michael.wenz>
Component:	Buckminster	Assignee:	buckminster.core-inbox <buckminster.core-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Michael Wenz

2010-10-01 07:20:22 EDT

I have two main features, let's call them feature and feature.examples. For 
both obviously source features exist: feature.source and examples.source.

Besides there is our SDK feature consisting of all 4 features from above 
(convenience for downloading).

If I now define different sequences of the included features in my site feature (the one that is being built using Buckminster's site.p2.zip action) in the build succeeds or fails:
Success: SDK.feature, feature, feature.examples
Failure: feature, feature.examples, SDK.feature

So far this is only reproducable on the Eclipse Hudson build server. A failed build is available here: https://hudson.eclipse.org/hudson/job/gmp-graphiti-nightly/389/ . Build 390 succeeded and the only change was the above described one.

I tried to reproduce this with an IDE-based Buckminster build but didn't succeed so far (neither on Windows nor on a Linux machine). I'll continue to try...

Michael