[Acceleo] Unstable behavior when using a query from an imported module [message #874034] |
Sat, 19 May 2012 20:10 |
|
Hello, I hope you can help me.
I have two modules in the same package of my project. The module A contains the following query:
[query public getOutputs(anAction: Action): Sequence(OutputPin) =
anAction.output
->select(op: OutputPin | op.isBBOutput())
->asSequence()
/]
Then, I import module A in module B and use getOutputs in the following query in B:
[query public getOutputsMultiplicities(anOperation: OpaqueAction): Sequence(Integer) =
anOperation.getOutputs()
->collect(op: OutputPin | op.getMultiplicity())
->asSequence()
/]
The behavior is unstable when building the project because Acceleo indicates the following error in getOutputsMultiplicities():
Iterator variable must have same type as source element type (anOperation.getOutputs()->collect(op : OutputPin | op.getMultiplicity())) Iterator variable must have same type as source element type (anOperation.getOutputs()->collect(op : OutputPin | op.getMultiplicity()))
When I clean and build the project the error disappears, but reappears whenever I do any modification in the file containing module B.
¿Any idea what is going on?
Thanks.
/TB
|
|
|
|
|
Re: [Acceleo] Unstable behavior when using a query from an imported module [message #874128 is a reply to message #874050] |
Sun, 20 May 2012 02:42 |
|
I installed Acceleo 3.3.0 M7 from the following repository:
http://download.eclipse.org/releases/juno
The problem seems to be no more. However, the perspective list tab in my workspace got a bit messy; no big deal. I installed Eclipse Juno M7 and all of my modeling infrastructure (Papyrus, Acceleo, OCL Editors and ATL), but when I opened my models in Papyrus, their layout changed, the icons for the applied stereotypes went small, and some elements were MISSING (although not in the .uml file in XMI).
I hope the Juno team and the Papyrus team fix issues by the official release day of Juno.
Thanks.
/TB
|
|
|
|
Powered by
FUDForum. Page generated in 0.03165 seconds