| Externalize workflow settings in xtext 1.0 [message #554536] |
Mon, 23 August 2010 09:51  |
Heiko Tappe Messages: 13 Registered: March 2010 |
Junior Member |
|
|
In xtext 0.7.2 I used to have a properties file to externalize some settings into a separate file.
I could refer to the settings via
<workflow>
<property name="propsfile" value="workflow/DslToCode.properties"/>
<property file="${propsfile}"/>
...
What would be the easiest/best way to do something similar in xtext 1.0?
--Heiko
[Updated on: Mon, 23 August 2010 09:51] Report message to a moderator
|
|
|
| Re: Externalize workflow settings in xtext 1.0 [message #554550 is a reply to message #554536] |
Mon, 23 August 2010 10:05   |
Sven Efftinge Messages: 1667 Registered: July 2009 |
Senior Member |
|
|
You should write an MWE2 workflow which just defines the properties (you
prevously had in the properties file) and calls the main mwe2 component.
Something like this:
module Caller
@my.MainModule {
property1 = "foo bar"
property2 = true
property3 = ComplexStuff { foo="bar"}
}
Am 8/23/10 3:51 PM, schrieb Heiko Tappe:
> In xtext 0.7.2 I used to have a properties file to externalize some
> settings into a separate file.
> I could refer to the settings via
>
> <workflow>
> <property name="propsfile"
> value="workflow/KomalogDslToCode.properties"/>
> <property file="${propsfile}"/>
> ..
>
> What would be the easiest/best way to do something similar in xtext 1.0?
>
> --Heiko
--
--
Need professional support for Xtext or other Eclipse Modeling technologies?
Go to: http://xtext.itemis.com
Twitter : @svenefftinge
Blog : http://blog.efftinge.de
--
Need professional support for Xtext and EMF?
Go to: http://xtext.itemis.com
Twitter : @svenefftinge
Blog : blog.efftinge.de
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.01701 seconds