That seems like the likely culprit. Setting JDK to “Java 1.7” in the job configuration got things running again. Otherwise, it was trying to run with some build of Java 5.
- Konstantin
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Matthias Sohn
Sent: Thursday, May 16, 2013 1:35 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Changes to JDKs on Hudson?
On Thu, May 16, 2013 at 10:13 PM, Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx> wrote:
Sapphire started failing with the following when running on eclipse.org Hudson.
Unable to load a script engine manager (org.apache.bsf.BSFManager or javax.script.ScriptEngineManager)
The problems seems to be related to running with an old version of JDK. Have there been any changes to what JDKs are installed on Hudson and what is used for the build?
If your build doesn't explicitly specify which JDK should be used it may be affected by the
resolution of bug 407265 [1].
