I can confirm that this was the same error I was seeing when trying Java 11
using Struts 2.5.18. It is happening in the convention pluggin on the startup
of the server when it scans for actions to configure Struts. It is not a
compile issue, but happening at runtime.
Paul
-Original Messa
In the end: yes. Although we are building with ANT and IVY.
But the compiler levels are specified as 11, yes.
I do not know how to do it with maven. But it woul dbe relevant for the
tests of the convention plugin to analyse some Struts2 action class with
class version 55.
Am 18.01.2019 um 09:
To clarify, you run your build on JDK11 and you defined source & target in
Maven pom as version 11, right?
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
pt., 18 sty 2019 o 09:09 Sebastian Götz
napisał(a):
> I took a short look. In Travis I can see that you run the build under
>
I took a short look. In Travis I can see that you run the build under
OpenJDK7.
We compile our sources with JDK 11 and source and target version 11
resulting in class files with class version 55.
Thus ASM cannot inspect our class during startup because of the usage of
the ASM5 API (restricts cla
4 matches
Mail list logo
