Community
Participate
Working Groups
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.
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.
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
