Hi Adolfo
It's all (OCLinEcore, OCLstdlib, but not CompleteOCL)
pretty much working, so I started to move on.
a) I would like to have preliminary UML support in M5 so
that Papyrus can try to use it.
- since Pivot is UML based the Pivot to UML conversion is
not too hard
- I did a first draft a few weeks ago
- activated it this morning
- .. then something broke hope to fix it this
evening
- oops UML has profiles ... a bit more
work
b) I would like to move the OCL Console to use the Xtext
Essential OCL editor
- reuse the Papyrus context entry point
- achieve consistent behaviour, accurate
evaluation
- don't want to do this in the branch, so waiting till I
can do it as a simple
experiment, Bugzilla, approval, release
c) Complete OCL ...
But there is something bad about my M4plus
workspace.
- no EMF source attachments
- Acceleo/MWE/Xtext build scripts are
temperamental
I'm waiting for a clean M5 before
investigating.
The workspace is pretty much as before,
but:
Xtext now needs GEF, so add it.
EMF is bigger; use just the SDK not the
All-in-One.
There are I think two new plugins
o.e.o.examples.library
I'll try to promote the branch this evening, maybe
tomorrow. I guess it doesn't actually need to work
for you to build it; there are 206-odd tests in the xtests
plugin that pass; mostly these are evolved
from Laurent's excellent tests; a few are from the old test
suite. The rest remain to migrate.
Regards
Ed
Ed,
I'm one of those Google's Calendar Users...
I'm
afraid that we only have this week to integrate with Xtext
2.0.0....
I've worked around the problem we had with hudson's build...
Although it looks like a couple test cases are failing ... Before looking into
this, I'd like start the builds against Xtext 2.0.0 so that I could save some
time (which is currently very limited) while trying to fix all the fix
toguether.
How is the xtext integration progressing ?
Best
Regards,
Adolfo.
-------- Mensaje original --------
The SimRel Planning Calendar (on Google) has had
Indigo M5 date incorrect until just now, this morning.
It was off by one week, one week late.
The actual plan document at
http://wiki.eclipse.org/Indigo_Simultaneous_Release
had the dates
listed correctly in its table:
M5
Friday, February 4, 2011 01/28 to
02/04
The other sense of
"correctness" has to do with comparing to last year's (Helios) dates, as well
as M6 and other Indigo dates.
Even
though the Google calendar is meant as a secondary "aide", I know many start
to depend on it as the final authority (myself included) so I know this typo
that I made long ago will effect some of us, and I can only hope not too much.
But, I do think best to adjust now, rather then "mess up" M6 and other dates.
See bug
355184 for the tracking report, or to
leave comments.
Please consider the environment before printing a hard copy of this
e-mail.
The information contained in this e-mail is confidential. It is intended
only for the stated addressee(s) and access to it by any other person is
unauthorised. If you are not an addressee, you must not disclose, copy,
circulate or in any other way use or rely on the information contained in
this e-mail. Such unauthorised use may be unlawful. If you have received
this e-mail in error, please inform us immediately on +44 (0)118 986 8601
and delete it and all copies from your system.
Thales Research and Technology (UK) Limited. A company registered in
England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne
Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number:
774298
Thales UK Limited. A company registered in England and Wales. Registered
Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone,
Weybridge, Surrey KT15 2NX. Registered Number: 868273