Granger wrote:Why do you push an update that breaks functionality?
Because I personally didn't have issues with that functionality being removed. And no one has really complained yet that they were using it.
Nashorn didn't support new and cool things from newest ECMAScript standards. So it had to go.
Not worth it using Nashorn for some odd functionality that maybe somebody sometimes uses, which is very thread unsafe anyway.
If you used this functionality and want it back, perhaps we can discuss about possible ways of replacing it with something.