Hi Adolfo
Xtext moving to 2.0 at M5 will clearly break the current MDT/OCL
Examples, so remove the Xtext editors to avoid breaking the Indigo
integration unless...
A lot of things came together over the weekend.
I was able to start using the pivot-model based Xtext editors to:
- edit constraints in the OCL standard library definition model
- see pivot-level semantic errors in the editor
- auto-generate the OCL Standard Library chapter pretty-printing the
constraints from AST models
Generally the branch now looks promising, so I'm about to migrate to
Xtext 2.0.0M4 and perhaps later nightlies and will hopefully promote
the branch just in time for M5. Flaky editors will at least be
better than no editors.
That gives us/me M6, M7 ... to fix the bugs. At least this year
we're bug fixing from M5, rather than starting development at M6.
Regards
Ed Willink
-------- Original Message --------
Hi all,
for M5 we (Xtext) will promote the 2.0 stream to the indigo builds, which contains some API changes.
We would like to help any clients updating/migrating their code and would kindly ask to inform us if you use Xtext somehow.
I know the Ecore Tools do and we are already in contact with Ed Willink.
Are there any other projects consuming Xtext?
Best Regards,
Sven
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1191 / Virus Database: 1435/3384 - Release Date: 01/16/11
|