Hi Anthony
My understanding is that GMF uses QVTo which is using OCL 3.0. Any
attempt to mix and match OCL 3.0 and OCL 1.4 is doomed to be a major
time waster.
OCL 1.4 was a well-intentioned but misguided attempt to maintain exact
API and OCL '2.0' specification interpretation compatibility. Ed Merks
killed this managerially last week by instructing us not to deliver two
OCLs to Helios, and practically by introducing an 'API' change into EMF
that makes preservation of exact API compatibility far too difficult. I
certainly won't be working on OCL 1.4 and so far I'm the only OCL
committer who's had time to make significant code contributions. As far
as I'm concerned OCL 1.4 is dead.
For the record the problem with OCL CVS was trivial and was only
apparent on IBM SDK 5.0. Five files contained incorrect UTF-8 encodings
of an a-acute in comments. These have now been corrected, and the
latest Hudson 3.0 build is green. The Hudson 1.4 builds show a thundery
state (316 attempts with no successes); probably still under
development.
As I do not have releng access, I do not have the opportunity to test
or monitor builds, so only became aware of a problem when Ed broadcast
to the world that everything had collapsed. My builds on Windows were
all fine. Over the weekend I found out about the Hudson CBI interface
(very useful) and so can now watch it. I hope that I will be granted
releng access soon so that I can perform builds more often than every
six hours and can promote successful builds.
Regards
Ed Willink
Anthony Hunter wrote:
Hi Ed,
I was on vacation last week so apologies for any delay on my part.
I have no idea what the latest OCL plan is, but I have been building
EMF validation and GMF with OCL 1.4.
I created Helios builds for EMF validation and GMF the last week of
November with OCL 1.4 M2. These builds were required due to changes at
the platform (https://bugs.eclipse.org/bugs/show_bug.cgi?id=296177
and https://bugs.eclipse.org/bugs/show_bug.cgi?id=296176
).
Since M4 is almost upon us, I suggest we stick with OCL 1.4.
Cheers...
Anthony
--
Anthony Hunter mailto:anthonyh@xxxxxxxxxx
Software Development Manager
IBM Rational Software: Aurora / Modeling Tools
Phone: 613-270-4613
Ed Merks
---2009/12/04 07:07:28 AM---David,
David,
JWT isn't a modeling project.
I'm a little concerned to see folks like Christian Damus and Richard
Gronback as contact points for the projects given they are no longer
committers. I'm also concerned at the state of CVS with the recent
changes to OCL. It appears that a large portion of the modeling
technology stack simply can't build right now, with GMF, QVT, Query,
and Validation all appearing to be broken to me. Some of the folks on
the CC list really need to take immediate steps to address the
outstanding issues or we're headed for a train wreck.
Regards,
Ed
David M Williams wrote:
As mentioned on another thread, I've updated the starter "participating
projects" page,
http://wiki.eclipse.org/Helios/Participating_Projects
with a little more top level organization, and added the following
guidance at the
top of the page:
[Note: the data that's currently there was just a quick edit of last
years data to provide a starting point. As projects fill in the table,
be sure to discuss with your PMC and Project Chain and Project Peers.
It is desired to consolidate as many "rows" as can meaningfully and
legitimately be combined. In the end, each row should correspond to one
project review (that is, one set of Docuware for each row).]
Looks like we have 11 Top Level Projects now! Guess I forgot about that
"Runtime" one. :) And, appears to me there would be at least 25 "rows",
at a minimum.
If anyone sees any improvements to make, feel free.
Thanks,
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes internal
to the Eclipse Foundation. To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal._______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes internal
to the Eclipse Foundation. To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal.
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.709 / Virus Database: 270.14.96/2548 - Release Date: 12/06/09 07:30:00
|