Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326764 - Order of included features influences build success
Summary: Order of included features influences build success
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-01 07:20 EDT by Michael Wenz CLA
Modified: 2019-02-25 14:40 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Wenz CLA 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