"K3 Project" wizard with "User Ecore Basic Aspects With Melange" template leads to invalid Melange file

[ebousse]

When creating a new "K3 Project" with the "User Ecore Basic Aspects With Melange" template, the generated melange file has several problems, including:

• a wrong import (MetamodelExtensions does not exist anymore): import static extension fr.inria.diverse.melange.lib.MetamodelExtensions.*
• outdated keywords, such as metamodel (instead of language) or ecore (instead of syntax)
• an error in the transformations on MyMetamodelMT that "cannot be resolved as a type, even after generating the language runtime, for some reason

Example:

package packageName

import static extension fr.inria.diverse.melange.lib.MetamodelExtensions.*

metamodel MyMetamodel {
	ecore "platform:/resource//as/model/My.ecore"
	exactType MyMetamodelMT
}


transformation execute(MyMetamodelMT mymodel) {
	val root = mymodel.contents.head as MyMetamodel

	print("root: ")
	println(root)
}

@Main
transformation main() {
	val m1 = MyMetamodel.load("input/Simple.xmi",      MyMetamodelMT)
	
	execute.call(m1)
}

[dvojtise]

Additionnaly, only external language would make sense in case of mixed K3/Melange projects

For "normal / non external" languages, Melange copies the aspects in the runtime language. Thus the original aspect classes are useless when the language is deployed. they are used only at compilation time then at runtime only the copies are useful.

Inn case of external language, the contract is that the aspect doesn't changes the language signature, they only implements the predefined operations, thus the original aspect classes can be used.