That's the solution, thank you!
My maven-scr-plugin version had fallen badly out of date by re-building from
an archetype... bumped to latest version and I no longer need the -noverify
argument.
Thanks again :D
--
View this message in context:
http://apache-sling.73963.n3.nabble.com/java-lang
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
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
, with the
following:
Error during instantiation of the implementation object
(java.lang.VerifyError: Expecting a stackmap frame at branch target 13
Exception Details:
Location:
com/edliohelloworld/image_microservice/ImageServlet.unbindResolverFactory(Lorg/apache/sling/ap
