Yesterday I was brave enough to have a closer look to MPS 3.0 and tried to migrate my language project. As exiting I was before as disappointed I am now.
On two 64 bit Kubuntu systems with the openJDK 1.7 I can't open existing projects or create a new one with MPS 3.0. The window with the status bar just freezes. On a openSUSE system this part works fine, with openJDK and Oracle JDK.
The second problem was that the last migration scripts of a not cleaned project (containing files generated by MPS 2.5) take so much time and spread the terminal with so many messages, that I canceled the procedure (See MPS-18789
). Sometimes the migration also freezes.
After cleaning all generated files the migration succeeds after an adequate time. But now I am having a project (8 languages and 8 solutions) with errors everywhere. When I start the type check for the whole project my system I ran into an out of memory error. Doing this just for my main language leads to about 2000 errors. As far as I remember I could solve 8 automatically with quick fixes. After a short look to the errors I give up. Most of them I do not understand and I can't see a common reason. I've tried to optimize the imports and build the languages with errors, without success.
Before digging in the errors, I would really like to know which preconditions must be met in a MPS 2.5 project to migrate successfully to MPS 3.0. Is there any documentation about it?