Bug 424514 - Acceleo 3 expressions containing white space are not interpreted
Summary: Acceleo 3 expressions containing white space are not interpreted
Status: RESOLVED FIXED
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: 0.9   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-12-20 05:16 EST by Hugo Marchadour CLA
Modified: 2021-03-21 11:16 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hugo Marchadour CLA 2013-12-20 05:16:11 EST
The detection of Acceleo3 expression doesn't handle pre and post white spaces.
These expressions don't work (in VSM or Interpreter):
* " [self/]"
* "[self/] " 
* " [self/] "

We can make a "trim()" on expression or directly in the VSM property section editor.
Comment 1 Hugo Marchadour CLA 2013-12-20 07:23:14 EST
Or we should throw a warning during the VSM validation process (and a quick fix that trim white-spaces).
Comment 2 Hugo Marchadour CLA 2013-12-20 09:56:54 EST
I've pushed a DRAFT here https://git.eclipse.org/r/#/c/20120/
Comment 3 Hugo Marchadour CLA 2013-12-20 09:59:18 EST
Sample of warning:
Whitespace(s) in excess to be interpreted by AcceleoMTLInterpreter.
DefaultInterpreterProvider will be used instead of AcceleoMTLInterpreter.
You should replace " [self/] " by "[self/]"
Comment 4 Hugo Marchadour CLA 2013-12-20 09:59:38 EST
A quick fix could be added.
Comment 5 Pierre-Charles David CLA 2021-03-21 11:16:31 EDT
Acceleo 3 / MTL is more or less deprecated, and there is a simple workaround anyway ("[' ' + self/]"); closing as WONTFIX.