Eclipse Community Forums: M2T (model-to-text transformation) » Xtend pulls in JDT

Help

Home

Home » Modeling » M2T (model-to-text transformation) » Xtend pulls in JDT - why?

Show: Today's Messages :: Show Polls :: Message Navigator

Xtend pulls in JDT - why? [message #667021]

Mon, 25 April 2011 16:37

Volker Wegert

Messages: 182
Registered: July 2009

Senior Member

Hello,

I'm trying to reduce the size and complexity of a product that uses
Xtend and Xpand (using an embedded generator, the WorkflowRunner is
called programmatically), and I've run into the following issue. The
feature org.eclipse.xtend requires the feature org.xtend.typesystem.emf
that in turn contains the plug-ins org.xtend.typesystem.emf and
org.xtend.typesystem.emf.ui. (BTW, I didn't find it very helpful that a
non-.ui-feature contains a .ui-plug-in). The plug-in
org.xtend.typesystem.emf.ui now requires org.eclipse.jdt.core and
org.eclipse.emf.converter, amongst others. The .converter plug-in then
pulls in the emf.codegen plug-ins that in turn again require large parts
of the JDT. I end up with a rather messed up product (100 MB zipped
file) that contains parts of the JDT that appear in various locations.
At the moment, I'm trying to work around this by creating my own feature
that contains the Xtend and Xpand plug-ins, but that's less than
optimal. Is there any chance to remove the JDT dependencies or at least
make them optional?

Thanks
Volker

--
* Volker Wegert * http://www.volker-wegert.de/contact *

Report message to a moderator

Re: Xtend pulls in JDT - why? [message #667210 is a reply to message #667021]

Wed, 27 April 2011 12:41

Sven Efftinge

Messages: 1823
Registered: July 2009

Senior Member

You of course don't need the *.ui bundles.
Ignoring the features and just use the bundles should solve your problem.
Also feel free to file a bugzilla regarding the bad composition of features.

Sven

Am 4/25/11 6:37 PM, schrieb Volker Wegert:
> Hello,
>
> I'm trying to reduce the size and complexity of a product that uses
> Xtend and Xpand (using an embedded generator, the WorkflowRunner is
> called programmatically), and I've run into the following issue. The
> feature org.eclipse.xtend requires the feature org.xtend.typesystem.emf
> that in turn contains the plug-ins org.xtend.typesystem.emf and
> org.xtend.typesystem.emf.ui. (BTW, I didn't find it very helpful that a
> non-.ui-feature contains a .ui-plug-in). The plug-in
> org.xtend.typesystem.emf.ui now requires org.eclipse.jdt.core and
> org.eclipse.emf.converter, amongst others. The .converter plug-in then
> pulls in the emf.codegen plug-ins that in turn again require large parts
> of the JDT. I end up with a rather messed up product (100 MB zipped
> file) that contains parts of the JDT that appear in various locations.
> At the moment, I'm trying to work around this by creating my own feature
> that contains the Xtend and Xpand plug-ins, but that's less than
> optimal. Is there any chance to remove the JDT dependencies or at least
> make them optional?
>
> Thanks
> Volker
>

--
Need professional support for Xtext or other Eclipse Modeling technologies?
Go to: http://xtext.itemis.com
Twitter : @svenefftinge
Blog : http://blog.efftinge.de

Report message to a moderator

Previous Topic:	T2T
Next Topic:	How to remove fully qualified names to imports

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Nov 30 11:32:16 GMT 2023

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter