|Re: [mdt-papyrus.dev] EPL v2 for SysML 1.4 ?|
Thanks for all the answers.
âEclipse Papyrusâ is ok for me.
Does anyone have an objection?
I agree that moving everything to EPL2 in on go would be the best but due to the size of the project and the number of plugin, I donât think itâs possible. But if we agree on the new license then we can
- Change license for all incoming component release
- Change the license in Papyrus core/toolsmith for September
Can anyone confirm that there isnât any fishing dual licensing stuff ?
I recall that once upon a time "Eclipse Modeling Project" was very strongly recommended, but recent practice has changed; Eclipse Xtext, Eclipse Mylyn, Eclipse DLTK. I've migrated to Eclipse OCL, Eclipse QVTd. So I suggest Eclipse Papyrus. "Project" is bloat.
On 26/06/2018 14:38, Camille Letavernier wrote: