Domain classes are generated at the wrong time and the wrong path

[berezovskyi]

When the resource shapes have been defined in an external domain spec from the toolchain spec, regeneration of a single adaptor causes the domain spec of the service in the adaptor to be generated in the path as configured for the toolchain, and not the external domain spec.

Expected: no generation of the external domain spec takes place during the code generation of a single adaptor.

[yashkhatri]

@berezovskyi Can you please provide a sample project and steps to reproduce this issue?

[berezovskyi]

sure

• https://github.com/EricssonResearch/scott-eu
• branch "b-robot-emulator"
• folder "lyo-sandbox"

steps:

1. import 2 model-* projects into Eclipse
2. See https://github.com/EricssonResearch/scott-eu/blob/b-robot-emulator/lyo-services/model-domain-pddl/generator.properties. The right output folder for the PDDL domain spec code is https://github.com/EricssonResearch/scott-eu/tree/b-robot-emulator/lyo-services/domain-pddl
3. open the Toolchain model, the Toolchain diagram. Right click on the Twin and generate the code.

here is the "wrong" folder being generated:

[jadelkhoury]

@yashkhatri this is most likely not a bug, but a "feature". It is very confusing how the generator treats composition of modls into file. I sugest we setup a workshop to decide how it should work before we fix anything.