[modeling-pmc] [CQ 2342] QVT Abstract syntax support

[emo-ip-team@xxxxxxxxxxx]

http://dev.eclipse.org/ipzilla/show_bug.cgi?id=2342





--- Comment #19 from Ed Willink <ed@xxxxxxxxxxxxx>  2008-07-15 13:52:10 ---
1) It's only necessary to pull the qvtr examples; the qvtc examples are ok.

2) No problem, though its only the gratuitous html/javadoc that needs pulling.
The main content is only slightly dated. A functionality revamp to at least
merge the UMLX registration and the QVT OML browsing behaviours is appropriate. 

4)

edit and editor plugins should be free from @generated NOT's. Make sure you use
3.4 to regenerate; there were some very late genmodel fixes.

The model plugins have at least 80 important @generated NOTs and many more with
a removed @generated. The QVTBase plugin is prone to a mis-genmodel when it
gets confused about the two EcorePackages. This has to be manually fixed.

Make sure you have Java formatting templates appropriate for long term use,
otherwise we may chase some partial reformatting during code generation through
subsequent genmodels.

Regeneration at this point is very unwise. It should be the first activity
post-check in to CVS so that the differences are persisted. If you do it
pre-check in we cannot trace the history and diagnose accidents.

I just did a quick test and regenerating does not change copyright headers, so
I think that what is required is a global insertion of your suggested copyright
text within 800 odd occurences of 

 * <copyright>
 * </copyright>

by something better (your text is fine).

That done the 10 to 20 residual *.properties files can be done by hand.


-- 
Configure CQmail: http://dev.eclipse.org/ipzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the CQ.