[news.eclipse.tools.emf] Re: Where have the "description.txt" files gone

[Ed Merks <Ed.Merks@xxxxxxxxx>]

Steve,

Comments below.

stephen crawley wrote:

Hi Ed,

Thanks for your quick response.

Below is the start of a "description.txt".  I guess that the clue to its origin is in the first few lines.  I was previously using an "EasyEclipse plugin warrior" distro (1.3.0.3), and I guess it has that "example" plugin installed as standard.

As, it's all coming back to be now.

OK.  So given that this file is not an official EMF artifact, would it be possible to make it an official artifact in the next EMF release?

Well, it really is meant to be an example, and I'm not really keen on the idea of adding this since then we'll also need a flag to control whether it's generated or not since most people won't want it.  Someone wanted another of our examples to be made available as well:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=150502

But you can of course install our examples though we package them up in the 2.4 SDK so that you can unpackage them in your workspace.  If you export this into your dropins folder then you'll get what you need.

  A simple text version of a model is a >>really useful<< thing to have available, IMO.  And it is likely that the code for creating the file is floating around the source code repository somewhere.

Somehow I think a more complete HTML formatted form with cross links would be more useful.  In terms of a simple text form, I would imagine that Emfatic would be far better since it's actually a serialized form of Ecore; hopefully we can get Emfatic into a state where it provides builds and distribute it with the next release.  Another way to get our the source is described in the wiki:

http://wiki.eclipse.org/EMF/Getting_Source

BTW: I backtracked to my old EasyEclipse distro to regenerate the description file for the latest .ecore and .gencore files.  That has solved my problem for now.

-- Steve

-------------------------------------------

Model MSS

This model description is not a real EMF artifact. It was generated by the
org.eclipse.emf.examples.generator.validator plug-in to illustrate how EMF's
code generator can be extended.
This can be disabled with -vmargs -Dorg.eclipse.emf.examples.generator.validator=false.

Package mss <http://au.edu.archer.metadata.msf/mss/1.0>

 Class Node
   Attribute description : InternationalText<<0..*>>

 Class NamedNode -> Node
   Attribute name : Name
   Attribute label : InternationalText<<0..*>>
   Attribute uri : EString
   Attribute /effectiveLabel : EString
   Attribute /effectiveUri : EString

...