Sort of solved: adding -noverify to the JVM arguments stops this error from occurring.
However, I don't fully understand the cause and I'm also nervous about forward compatibility... I wonder how this could prevent us from moving to future Java versions. It just seems like a bad smell that stable behaviour depends on an esoteric JVM flag. -- View this message in context: http://apache-sling.73963.n3.nabble.com/java-lang-VerifyError-tp4070000p4070001.html Sent from the Sling - Users mailing list archive at Nabble.com.
