TGG Project Wizard should add dependencies for meta-model projects

[RobinOppermann]

When creating a new TGG project, the wizard lets the user choose the meta-models for source and target.
If the meta-models belong to eMoflon EMF projects, it would be nice to automatically add these projects as dependencies, so the user does not have to do it himself, or wonders why the types cannot be resolved (e.g. in the weight language)

[Arikae]

I don't fully understand this issue.
Why should we import eMoflon specific meta-models by default?
I do not expect the standard user to work with our internal meta-models so I'm not sure why this might be a problem.
Even if you do implement such a TGG, it is not sure which of our meta-models you are needing and I would rather not import meta-models which may not be used.
Could you clarify this issue a bit more?

[anthonyanjorin]

Hi @Arikae

what Robin means is that if an .ecore is chosen as a dependency, and it happens to be in an eMoflon project with generated code, then we should automatically add the project as a plugin dependency.

Clear?

Tony

[anthonyanjorin]

Any progress? Have you been able to reproduce?

[maxkratz]

I do not know if it is still relevant (probably not), but I can reproduce it.
+1 for automatically adding the source metamodel and the target metamodel to the dependency list in MANIFEST.MF of a newly created TGG project.