Ed,
It looks promising :)
Our M5 milestones is targeted on Monday, the 7th in February... as
soon as the source code is aligned to Xtext 2.0.0 let me know it to
make our builds be feeded by Xtext nightly repository.
On the other hand, I'm currently involved in a project at work, so
my time to spend in Open Source projects gets again decreased. I
think that the releng is quite stable. Perhaps, I could spend some
time to improve the documentation concerning our public composite
repositories and minor hints concerning buckminster...
So, I could then either:
- Start the creation of different jobs to create different
artifacts/repositories for the MDT/OCL Core (our current SDK) and
MDT/OCL (our current examples).
- or, Start to review of the development stuff (Axel's patches,
pivot model, etc,... ).
In principle, we could survive without the MDT/OCL Core and Tools
split (as we have been doing so far). However as you know, creating
an stable repository at +1 with the examples depending on Xtext
could be risky. We should probably need to create nightly,
integration and stable builds using the Xtext nightly repository to
avoid surprises at +3 (and +4).
Best Regards,
Adolfo.
El 17/01/2011 8:42, Ed Willink escribió:
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
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
|
