I’m trying to implement some automatic test generation using xText, xPand and MWE. I managed to create code files but I wanna create them in a organized package structure. Do you know how can I create packages using those tecnologies?

Thank you for all,

Cheers,

I think there’s a typo:
should be
vetostrategy class=”someFullyQualifiedClassName” path=”src-man”
instead of …src-gen

there’s anotherone (at least if using oAW 4.3.1):
should be vetoStrategy
instead of vetostrategy
otherwise the workflow doesnt find the add() methode

ekke

Hi Stefano, I am thinking about a similar approach to overcome problems with generated artifacts under version control where a separate workflow component checks such a “ghost” directory against the newly generated output. This could overcome annoying problems with directories that have to be deleted. Ever implemented anything in that direction?

we have implemented an adapted version of the generate once pattern. The content of the src-once directory is backuped before the generation process is starded. src-once is then fully cleaned et re-generated. In a third step, the classes that can be found in src-once AND in the backup directory are restored while all other classes are ignored. In this way the ghost classes (ConcreteA in your example) are deleted, the manually customized classes are preserved and the new classes are generated.
The save and restore processes are implemented as quite simple OAW-Components an can be integrated in a Workflow. The same strategy could be naturally also implemented as an ant build.
Thank you for your excellent post.
Stefano