Ed,
The reason I set nithglies repositories (when possible) for the
projects we depend on is that we may react to breaking changes as
soon as possible, rather than realizing about such a changes during
the milestone weeks...
So yes, I prefer that we use the latest code of our dependent
projects ... If I needed to build to do/check some releng fixes,
either I'd wait until the code is updated and the build is ok or I'd
change by myself the use of a older repository. However I don't
think to do the latter if it's not really necessary.
Best Regards,
Adolfo.
El 16/02/2011 10:21, Ed Willink escribió:
Hi
Adolfo
Main failure seems to be removal by Xtext of
org.eclipse.xtext.common.types.JvmIdentifiableElement.getCanonicalName().
Once I've downloaded a nightly, I'll see if there's a
backwards/forwards compatible fix. Otherwise we'll have to use a
close approximation to Xtext M6 for our M6.
There is an alternate getIdentifier() method, but no overlap, so
compatibility would require reflective access to either
getCanonicalName or getIdentifier.
Do you want to freeze the builds at M5 Xtext, or accept that our
working workspaces must use a recent Xtext nightly? I guess the
latter will have fewest problems at M6.
Regards
Ed
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
|
