MPS 3.x and Java 8

Hi, Dan.
Yes, we are waiting for a possibility to switch to J7 or J8. At least because we have problems with classloading process in J6 (it's not extensible enough for us).
The only thing we'll have to wait for is Idea platform switching to J8 (as we work on the top of it).
So, I wouldn't say we'll do this right in March, but sometimes we definitely will.

Thanks Mihail,

i have another question regarding the import of *.jar files. Using MPS 3, a total of 128 jars get imported (obviously i have some dependency on MPS.Core). Would it be clever, to import *.jar files always via a solution, and not via a language? Couldn't i manage imports and dependencies in a more subtler way then?

E.g. the baselang collection language dependes on the collection solutions, which imports a runtime jar. I have a lot of spring-framework jars i would import via a solution and let the language depend on the solution ..

Dan

Hi all,

i manged to develop some answers to my question myself. My investigations lead me to the conclusion that external jars should be imported as stubs via solutions. Languages depending on those jars can depend in turn on the solution. The advantage is that other modules - depending also on those jars - could solely use the solution without the language. Most of the time, languages come with additional dependencies we can get rid off when using solutions for import. Less dependencies this way ...

Dan

Most of the time, languages come with additional dependencies we can get rid off when using solutions for import. Less dependencies this way ...

a lot of things like plugins, actions and actionGroups etc work with a solution (as against language as in previous editions of MPS) in newer MPS versions.Guess it's related but...

Is it possible to have a peek into  the class-loader design patterns for solution vs language imports as a document or may be a link i could see?