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

Bug 338135

Summary: Zest Dependencies updated or in another feature
Product: z_Archived Reporter: Miles Parker <milesparker>
Component: BuckminsterAssignee: buckminster.core-inbox <buckminster.core-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3 CC: steeg, thomas
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Miles Parker CLA 2011-02-24 13:33:54 EST 
The buckminster dependency visualizer has a dependency on major version dependency on Zest 1.3.0. Since that is part of buckminster.core feature it prevents buckminster from being installed in the same platform as the new Zest. The Zest 2.0 api is quite similar to the 1.3.0 API so it *may* be possible to widen the version requirement. Otherwise I guess it would be necessary to require Zest 2.0 in which case that would exclude pre-Indigo builds. So perhaps it would make sense to move the depdency visualizer into its own feature.
Comment 1 Thomas Hallgren CLA 2011-02-25 06:52:21 EST 
As I recall, the upper bound was put there because our build broke in Helios if we didn't. That in turn is because Zest 2.0 is in the repository that you contribute to Helios. You limit that in your b3aggrcon file but that doesn't help us much since we consume the repository as input to our builds.

I guess with Helios SR2 out of the way we should be able to remove the upper bound unless there are any API changes that will break our build. I'll look into that.
Comment 2 Thomas Hallgren CLA 2011-03-05 06:24:36 EST 
The org.eclipse.zest.core dependency was relaxed to >=1.2.0 instead of [1.2.0,1.3.0) and the org.eclip

 se.zest.layouts dependency was relaxed to >=1.1.0 instead of [1.1.0,1.2.0).

Fix released to trunk, rev 11674