Using DSL-Editor in an older Eclipse [message #1114946] |
Mon, 23 September 2013 12:54 |
Björn Rellesch Messages: 38 Registered: January 2013 |
Member |
|
|
Hello,
I want to use my DSL-Editor in an every-day-Eclipse. For the same version of Eclipse I can follow the description on the internet-site:
http://wiki.eclipse.org/Xtext/GettingStarted#Deployment
This works fine, if I use the same version of Eclipse for developing the DSL and the exported an deployed DSL-Editor.
But we want to decouple the developing of the DSL and the use of the Editor. Currently we use Kepler to develop the DSL. However we want to use the Editor in Indigo.
If I use the description from the link above I get some reasonable errors of missing some libraries.
Is there a way to export all required plugins so I can use the DSL-Editor in an older-versioned Eclipse?
("Reexport this dependency" and installing Xtext does not fix my problem)
Eclipse- and Xtext-Version, which was used to develop the DSL:
Kepler Build ID: 20130614-0229, Xtext 2.4.3
Eclipse, which is used in every-day-work:
Indigo Build id: 20110916-0149
Greets Björn
[Updated on: Mon, 23 September 2013 13:00] Report message to a moderator
|
|
|
Re: Using DSL-Editor in an older Eclipse [message #1114999 is a reply to message #1114946] |
Mon, 23 September 2013 14:10 |
|
On 23/09/2013 14:54, Björn Rellesch wrote:
> Hello,
>
> I want to use my DSL-Editor in an every-day-Eclipse. For the same
> version of Eclipse I can follow the description on the internet-site:
> http://wiki.eclipse.org/Xtext/GettingStarted#Deployment
>
> This works fine, if I use the same version of Eclipse for developing the
> DSL and the exported an deployed DSL-Editor.
> But we want to decouple the developing of the DSL and the use of the
> Editor. Currently we use Kepler to develop the DSL. However we want to
> use the Editor in Indigo.
>
> If I use the description from the link above I get some reasonable
> errors of missing some libraries.
> Is there a way to export all required plugins so I can use the
> DSL-Editor in every older-versioned Eclipse?
> ("Reexport this dependency" does not fix my problem)
>
>
>
> Eclipse- and Xtext-Version, which was used to develop the DSL:
> Kepler Build ID: 20130614-0229, Xtext 2.4.3
>
> Eclipse, which is used in every-day-work:
> Indogo Build id: 20110916-0149
>
> Greets Björn
Hi
If you use a target platform with Xtext 2.4.3 and Indigo Platform this
should work... are you using a target platform at all?
cheers
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
|
|
|
|
Re: Using DSL-Editor in an older Eclipse [message #1115633 is a reply to message #1114946] |
Tue, 24 September 2013 11:08 |
|
You would have to build a feature project containing you DSL, and build a p2 repository that contains that feature. The appropriate way to achieve this is to build your plugins with a build framework (Maven Tycho or Buckminster).
From the resulting p2 repository you could install your DSL feature into your Indigo installation. All dependent plugins will be installed if the appropriate repositories (i.e. your DSL repository and Xtext repository) are available.
See the developer guide of project Spray for details on build setup. Maybe not the "easy" solution you would like to have, but the right one. The approach described in the Deployment guide of the Xtext manual only suites for the trivial case that the DSL feature is installed on a predefined Xtext enabled local Eclipse distribution. In production this is usually not what you want.
Regards,
~Karsten
Need professional support for Xtext, EMF, Eclipse IDE?
Go to: http://devhub.karakun.com
Twitter : @kthoms
Blog : www.karsten-thoms.de
|
|
|
Powered by
FUDForum. Page generated in 0.04018 seconds