This error is usually caused by an old version of ASM that is used for writing the implementation of the bind/unbind methods of references if such functions do not already exist.
This usually stems from the use of an old maven-scr-plugin, and upgrading to a newer one will most usually fix this, or you can write the java code for bind/unbind yourself (so they are not auto-generated incorrectly). I don't remember what all was in Sling8, so not sure if you could migrate to the now preferred OSGi R6/DS 1.3 annotations instead... On Tue, Jan 31, 2017 at 7:28 AM, lancedolan <lance.do...@gmail.com> wrote: > 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.