Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » plugin.xmi vs. plugin.xml
plugin.xmi vs. plugin.xml [message #687286] Fri, 27 May 2011 07:20
Eclipse UserFriend
Originally posted by:

I've have needed to work with various plugin.xml files a lot lately, and
then it struck me: Why not plugin.xmi, i.e. an instance of a plugin
model? plugin.xml is xml with a schema, right, so it shouldn't be
impossible to automate the translation of plugin.xml's and schemas to a
combination of plugin models and instances (and back). I think the
biggest difficulty is how a plugin.xml combines many kinds of instances
in one file:
- the top-level xml elements are instances of a plugin model (plugin,
extension and extension-point elements), lets call it plugin.ecore
- an extension-point and its associated schema (exsd) introduces a new
model, lets call it <extension-point-name>.ecore
- an extension is an instance of the corresponding <extension-point>.ecore

So, a plugin.xml could be translated to one plugin.xmi and a set of
<extension-point-name>.ecore files.

If this worked we could 1) use EMF to manage plugin.xml and 2) as a
side-effect be able to support merging of plugin.xml when generating EMF
plugin projects (edit & editor).

Just an idea...

Hallvard
Previous Topic:(no subject)
Next Topic:how to write a report error after parsering the grammar
Goto Forum:
  


Current Time: Thu Sep 19 02:03:53 GMT 2019

Powered by FUDForum. Page generated in 0.02077 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top