sebb>Regarding add-ons such as Nashorn I'm afraid you are missing the point. We never included it in the release packages. Nashorn is a part of the Java since http://openjdk.java.net/jeps/174
The problem with it is https://openjdk.java.net/jeps/335 : Deprecate the Nashorn JavaScript Engine Vladimir ср, 9 окт. 2019 г. в 12:59, sebb <[email protected]>: > c) > > Regarding add-ons such as Nashorn: > > I think the project needs to think very carefully before including > such items in the binary packages in future. > Instead, just provide the API to link to the 3rd party package, e.g. > JDBC and JSR223. > > On Wed, 9 Oct 2019 at 10:41, Philippe Mouawad > <[email protected]> wrote: > > > > Hello Felix, > > c) as of me > > > > Regards > > > > On Wed, Oct 9, 2019 at 11:36 AM Felix Schumacher < > > [email protected]> wrote: > > > > > Hi all, > > > > > > I have used a test plan with a lot of JavaScript snippets with Java 11 > > > and got really annoyed by the deprecation warnings that nashorn emits. > > > > > > They can be silenced by adding > "-Dnashorn.args=--no-deprecation-warning" > > > to the java command line parameters. > > > > > > Should we > > > > > > a) add them when we detect a current Java version > > > > > > b) add a comment in the start scripts > > > > > > c) add it to the known problems section > > > > > > d) do nothing > > > > > > e) do something completely different > > > > > > (and should we do this before the next RC?) > > > > > > My preference is c) (with a) as second best) and before the next > release. > > > > > > My solution at work was to add it with an entry in setenv.sh > > > > > > Regards > > > > > > Felix > > > > > > > > > > -- > > Cordialement. > > Philippe Mouawad. >
