Hi
I think MWE2 needs to use a modelpath that is analoguous to a classpath
but without making Eclipse think that there is a dependency. I would
gladly provide explicit 'import' statements in the Standalone bean setup
so long as there is a syntax that enables platform:/plugin to correctly
resolve to platform:/resource if present else platform:/plugin in the
normal EMF fashion.

Maybe I'm confusing two problems:

a) spurious classpath entries/scanning

My StandaloneSetup config is

bean = StandaloneSetup { resourceSet = resourceSet
platformUri = "./META-INF" // A local folder to
minimize workspace searching
scanClassPath = true // But we do need to search
the plugin-space
uriMap = Mapping {
from = "platform:/plugin/org.eclipse.uml2.uml.resources/"
to = "platform:/resource/org.eclipse.uml2.uml.resources/"
}
uriMap = Mapping {
from = "platform:/plugin/org.eclipse.uml2.uml/"
to = "platform:/resource/org.eclipse.uml2.uml/"
}
}

which scans (everything on) the classPath to enable a standalone usage
to find the two UML plugins that I'm interested in as platform:/resource
names that I can then map to the platform:/plugin names that need
resolving. A more direct

modelPlugin = "org.eclipse.uml2.uml",
"org.eclipse.uml2.uml.resources", "org.eclipse.xtext.common.types"

could support the accesses that I really wanted without needing a
spurious Java classPath entry or scanning every possible plugin.

[I find that MWE's brute force attempts to find everything as well
intentioned but actually unhelpful through depriving users of the
required declarative control and they are very very costly; an MWE
script can easily take 10 seconds before its 'time 0' diagnostic.]

b) cyclic Java class paths

In order for the MWE script to access the *.xtext file, the editor
plugin must be on the class path of the build plugin containing the MWE
script. If the MWE script generates Java into the editor plugin then the
MWE script modifies something on the build plugin classpath, potentially
triggering a rebuild 'cycle' that does not actually rerun the MWE script
but does re-re-build all the transformation templates in the same build
plugin as the MWE script.

If instead an Xtext file was located via a StandaloneSetup import
declaration such as

modelPlugin = "org.eclipse.ocl.examples.xtext.oclinecore" // etc

the Java classpath would not serve a double purpose, the editor plugins
could be omitted from the classpath and the rebuild 'loop' is not created.

That should only be the case if the edited Java file is referenced.

15 seconds still is too slow. Is that the project build or what happens when you save a single file?

BTW: You should consider having more smaller files. That's not only a good idea for performance reasons.

Sven Efftinge wrote on Wed, 31 August 2011 16:07

BTW: You should consider having more smaller files. That's not only a good idea for performance reasons.

I'll give it a try but it will require a lot of refactoring since there are quite a lot methods which depend on each other and often use dispatching.

This is an Eclipse Update site/p2 repository; you must access it from
Eclipse.

Regards,
Dennis.