No, this definitely isn't a good thing. We must tolerate and even
support 3.x so we must build and test against that. If we don't do
that, we've basically made this decision for a large fraction
(majority) of the release train which I don't feel is appropriate.
The platform team has made it clear that 4.x must be compatible with
3.x so anything in EMF we discover (or downstream clients discover)
doesn't work with 4.x will be something the e4 team needs to
address. We need to change this as soon as possible...
Hopefully we'll be able to upgrade our builds so that the build is
done and tested against 3.x and then retested against 4.x, but
that's a longer term goal..
Regards,
Ed
On 23/09/2011 9:05 AM, Kenn Hussey wrote:
Michael,
The dependency versions for EMF are determined at build time
based on the target it is built against. Since we built EMF 2.8
M2 against Eclipse 4.2 (given that the Juno train is being based
on 4.x), the dependency versions are based on 4.2... We could
switch back to building against 3.x but then we'd have less
confidence that things work properly in 4.x...
while switching
the EMF version we use from 2.7 to 2.8 I noticed a
strange dependency within org.eclipse.emf.edit.ui:
the EMF 2.8 version has a plugin dependency to
org.eclipse.ui.workbench[3.102.0,4.0.0).
The real problem
appears when we try to build against the Eclipse 3.8
milestones update site for M2: there is only
org.eclipse.ui.workbench in version 3.8.0 available
which causes an unresolved plugin error. The Eclipse
4.2 milestones update site for M2 contains two
versions of org.eclipse.ui.workbench (versions 3.8.0
and 3.102.0).
Any thoughts? It
appears at least strange to me. What is the purpose
behind?