Minimal Runtime Configuration [message #1725532] |
Fri, 04 March 2016 08:34 |
|
Hello,
I have a question about the minimal runtime. Is there a documentation of how to select features of the Sirius runtime. We want to have a minimal configuration with only the features needed to run our editor.
Thanks and regards,
Lars
|
|
|
Re: Minimal Runtime Configuration [message #1725787 is a reply to message #1725532] |
Mon, 07 March 2016 16:08 |
|
Le 04/03/2016 15:53, Missing name Mising name a écrit :
> Hello,
Hi.
> I have a question about the minimal runtime. Is there a documentation of
> how to select features of the Sirius runtime. We want to have a minimal
> configuration with only the features needed to run our editor.
The org.eclipse.sirius.runtime feature contains everything a typical
Sirius runtime needs, excluding the parts only needed for the specifier.
The feature contains support for all standard Sirius dialects (diagrams,
tables and trees). If you only use some of them and really need
something minimal, you'll need to create your own feature inspired by
org.eclipse.sirius.runtime with the dialects you don't need removed.
You'll also need the runtime support for whichever query languages you
use in your VSMs, i.e. org.eclipse.sirius.runtime.aql if you used AQL
(recommended) and/or org.eclipse.sirius.runtime.acceleo if you used
Acceleo 3/MTL. The "var:/feature:/service:" pseudo-languages are
implemented in the core and do not need additional dependencies.
You may also need to have org.eclipse.sirius.runtime.ide.eef or
org.eclipse.sirius.runtime.ide.xtext if you want EEF or Xtext integration.
Regards,
Pierre-Charles
--
Pierre-Charles David - Obeo
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
Pierre-Charles David - Obeo
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
|
|
|
Re: Minimal Runtime Configuration [message #1725893 is a reply to message #1725787] |
Tue, 08 March 2016 10:55 |
|
Hello Pierre-Charles,
thank you for the information.
I checked with our setup and we have additionally the org.eclipse.runtime.ide.ui and org.eclipse.runtime.ide.xtext features included. The first one we need because we have quite a lot of dependencies to classes like DDiagramEditor or DDiagram or ModelProjectManager which come from the diagram.ui or sirius.ui bundle. The latter I am not sure whether we need it, but we use a combination of an XText language based approach together with Sirius.
My concern is that both the org.eclipse.sirius.ui and org.eclipse.sirius.common.xtext both need org.eclipse.jdt.core as a hard dependency. Since our tool has no requirement towards java, we would rather avoid adding jdk bundles to our product. Any idea for a solution?
Thanks,
Lars
|
|
|
|
|
Re: Minimal Runtime Configuration [message #1727378 is a reply to message #1727210] |
Tue, 22 March 2016 14:25 |
|
Le 21/03/2016 11:52, Pierre-Charles David a écrit :
> Le 15/03/2016 15:55, Esteban Dugueperoux a écrit :
>> Hi Lars,
>>
>> Indeed you point out a JDT/Sirius coupling.
>> For details :
>>
>> - org.eclipse.sirius.ui plugin contains ModelingToggleNatureAction which
>> use JDT API to get a IProject, not sure if this is really usefull
>
> It looks like it is not really needed anymore. I have a patch pending
> (https://git.eclipse.org/r/67965) which would remove it.
This is now merged and will be in Sirius 4.0M6. See
>> - org.eclipse.sirius.common.xtext plugin has a dependency to JDT to
>> support case of XText DSL using JVM types, see [1].
This one is now optional, see https://git.eclipse.org/r/#/c/68926/ (also
merged for 4.0M6).
>> Could you raise a bugzilla to highlight this issue?
There was already one actually: http://eclip.se/458751. See my comment
there for more details on the dependencies remaining.
Regards
--
Pierre-Charles David - Obeo
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
Pierre-Charles David - Obeo
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
|
|
|
Powered by
FUDForum. Page generated in 0.03390 seconds