search

diverse-project / melange

The Melange Language Workbench
http://melange-lang.org
Eclipse Public License 1.0
28 stars 7 forks source link

add the possibility to to define the name of the project that will host the generated Melange Language Runtime #79

Open dvojtise opened 7 years ago

dvojtise commented 7 years ago

Currently the Melange Language Runtime is generated in a project whose name is directly inferred from the full qualified name of the language in the melange file.

In some case it would be useful to be able to use a specific name for the hosting project. (in order to make clear that the project has been generated, or that it contains a MelangeLanguageRuntime for example)

In addition, this should also allow to generate this directly in the same project that host the melange file itself, so everything related to this language is in the same project (model type, adapters, and language runtime)

dvojtise commented 7 years ago

After discussion with @fcoulon, he think (and I agree) that simply adding an optional attribute in the .melange file is not the best solution because this is not part of the language definition but part of the build process. If we consider other tool approaches for this, we can see that both emf and xtext for example use an external file for build process customization (resp. .genmodel and .mwe2 files)

Should we have an equivalent file for melange ? something like .genmelange ? We could also make it optional in case the user doesn't want to change the default values.

@tdegueul what do you think would be the best solution ?

combemale commented 7 years ago

There will be some change with ALE and the .dsl file that will have impact. I propose to consider it in the .dsl file in a first attempt.

Benoit

Le 26 avr. 2017 à 08:18, Didier Vojtisek notifications@github.com a écrit :

After discussion with @fcoulon https://github.com/fcoulon, he think (and I agree) that simply adding an optional attribute in the .melange file is not the best solution because this is not part of the language definition but part of the build process. If we consider other tool approaches for this, we can see that both emf and xtext for example use an external file for build process customization (resp. .genmodel and .mwe2 files)

Should we have an equivalent file for melange ? something like .genmelange ? We could also make it optional in case the user doesn't want to change the default values.

@tdegueul https://github.com/tdegueul what do you think would be the best solution ?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/diverse-project/melange/issues/79#issuecomment-297386990, or mute the thread https://github.com/notifications/unsubscribe-auth/ADtBUJo5oyiz-92odsxcgdMSNOqxLe9Eks5rzzYIgaJpZM4M2kOQ.