Hello i've found a weard behavior after renaming a module. For demonstration purposes i've prepared a small example.
I created a new project with the following languages:
(Hint: 'language1' depends on 'language.base')
Now i want to rename the "rename.module.language.base" module to "rename.module.language.basics". To achieve this i've used the following method:
Step 1) Rename "rename.module.language.base" module to "rename.module.language.basics" via "Logical View" view
Step 2) Rename "rename.module.language.base" folder to "rename.module.language.basics" via "File System" view
Step 3) Replace old "rename.module.language.base" from "modules.xml" with "rename.module.language.basics" (Alt + Enter on project)
Step 4) Deleting the empty "rename.module.language.base" folder via system explorer (optional)
Step 5) Rebuild of the entire project.
It seems like everything went right, but when i check any ".mpl"/".msd" file of a module, that depends on the previous renamed module, the name of its dependency version (and language versions) is not up to date.
(Dependency itself is fine)
(Dependency versions is NOT)
It is possible to change the displayed name of the dependency version manually, but this takes a lot of time ('trial and error') if the renamed module is something fundamental, because you have to find all references (language/dependeny versions) AND hope that MPS doesn't readjusts the dependencies to older versions.
Is there any best practise in renaming modules so that other projects do not suffer from migration issues?
Thank you in advance and best regards