Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Strange dependency of EMF Edit UI

Thanks again Kenn, this solved our build error against Eclipse 3.8 milestone.

Michael

Von meinem iPad gesendet

Am 23.09.2011 um 19:48 schrieb "Kenn Hussey" <kenn.hussey@xxxxxxxxx<mailto:kenn.hussey@xxxxxxxxx>>:

Done.

On Fri, Sep 23, 2011 at 1:32 PM, Kenn Hussey <<mailto:kenn.hussey@xxxxxxxxx>kenn.hussey@xxxxxxxxx<mailto:kenn.hussey@xxxxxxxxx>> wrote:
M2a builds of EMF (and XSD) and UML2 have been posted to their respective repositories. I'll change the aggregator contribution and post download ZIPs shortly...

Kenn


On Fri, Sep 23, 2011 at 12:38 PM, Kenn Hussey <<mailto:kenn.hussey@xxxxxxxxx>kenn.hussey@xxxxxxxxx<mailto:kenn.hussey@xxxxxxxxx>> wrote:
Actually, if we post an M2a build for EMF, it should be possible for folks to build against it even if the platform (4.2) doesn't respin - by referencing the EMF milestone repository you should be able to pick up the right version depending on whether you are building against Eclipse 3.8 or 4.2.

I'll work on posting an M2a for EMF ASAP.

Kenn


On Fri, Sep 23, 2011 at 12:31 PM, Eike Stepper <<mailto:stepper@xxxxxxxxxx>stepper@xxxxxxxxxx<mailto:stepper@xxxxxxxxxx>> wrote:
Am 23.09.2011 18:27, schrieb Kenn Hussey:
OK. We can't switch this for M2 unless we respin the platform to pick up a new EMF M2a milestone. Otherwise, it will have to wait until M3.
This problem has hit us (CDO), too, and I'm not sure if we can wait until M3. As it seems now we just can't build against EMF 2.8. Or did I miss something?

Cheers
/Eike

----
<http://www.esc-net.de>http://www.esc-net.de
<http://thegordian.blogspot.com>http://thegordian.blogspot.com
<http://twitter.com/eikestepper>http://twitter.com/eikestepper




Kenn

On Fri, Sep 23, 2011 at 12:20 PM, Ed Merks <<mailto:ed.merks@xxxxxxxxx>ed.merks@xxxxxxxxx<mailto:ed.merks@xxxxxxxxx>> wrote:
Kenn,

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...

Kenn

On Fri, Sep 23, 2011 at 10:16 AM, Wenz, Michael <<mailto:michael.wenz@xxxxxxx>michael.wenz@xxxxxxx<mailto:michael.wenz@xxxxxxx>> wrote:
Hi,
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?
Michael

_______________________________________________
cross-project-issues-dev mailing list
<mailto:cross-project-issues-dev@xxxxxxxxxxx>cross-project-issues-dev@xxxxxxxxxxx<mailto:cross-project-issues-dev@xxxxxxxxxxx>
<https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev





_______________________________________________
cross-project-issues-dev mailing list
<mailto:cross-project-issues-dev@xxxxxxxxxxx>cross-project-issues-dev@xxxxxxxxxxx<mailto:cross-project-issues-dev@xxxxxxxxxxx>
<https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
<mailto:cross-project-issues-dev@xxxxxxxxxxx>cross-project-issues-dev@xxxxxxxxxxx<mailto:cross-project-issues-dev@xxxxxxxxxxx>
<https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev





_______________________________________________
cross-project-issues-dev mailing list
<mailto:cross-project-issues-dev@xxxxxxxxxxx>cross-project-issues-dev@xxxxxxxxxxx<mailto:cross-project-issues-dev@xxxxxxxxxxx>
<https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



_______________________________________________
cross-project-issues-dev mailing list
<mailto:cross-project-issues-dev@xxxxxxxxxxx>cross-project-issues-dev@xxxxxxxxxxx<mailto:cross-project-issues-dev@xxxxxxxxxxx>
<https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx<mailto:cross-project-issues-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Back to the top