@dpa-openhab Please continue the discussion in this thread.
I was thinking of this announcement:
https://blogs.oracle.com/java/post/detaching-graalvm-from-the-java-ecosystem-train
Reading it again, I realize that I might have misunderstood it. It might be GraalVM as a general JVM that is being discontinued, with a renewed focus on GraalJS and GraalPy. I’m not sufficiently informed about the “Graal ecosystem” to always know what is referred to and not.
Yes, I did mean “Core”. I’m not sure what you mean by “installed indirectly” - maybe I’m just using the wrong terms again, I’m talking about (I think) GraalJS and GraalPy - I’m not talking about the complete JVM. These terms just confuse me, because I don’t know where the lines are drawn.
If I still didn’t understand what you meant, please clarify 
I didn’t mean to move any code into Core. What I tried to suggest that if the concepts in JSR223 and “whatever we want to call the Graal thing, Polyglot?” mismatch, maybe it would be better to make “a second provider of scripting functionality” then trying to force everything through the “signatures” of JSR223.
JSR223 is still very useful, it can provide for support for many other languages than the two provided by Graal, so I’d hate for the needs of “the Graals” to diminish/limit the possibilities of actual JSR223 implementations, in an attempt “to make both fit” through “the same door”.
Regarding the languages server and the IDE bundles, I’m not sufficiently informed about those topics to understand what you mean.