It would be great if we could remove ASM3. My naive investigation suggests
that both ASM 3 and ASM 5 share some of the same clases in the same package
structure which are likely the cause of some of our issues. If it really is
that one class, it shouldn't be to complex. Regarding Spring and ASM
> From: lukaszlen...@apache.org
> Date: Sun, 12 Jun 2016 11:31:26 +0200
> Subject: Re: interfaces with default methods on actions
> To: user@struts.apache.org
>
> 2016-06-12 6:46 GMT+02:00 Johannes Geppert :
> > Is there still any reason to still use asm3?
> > Or should we
2016-06-12 6:46 GMT+02:00 Johannes Geppert :
> Is there still any reason to still use asm3?
> Or should we change this with 2.5.x?
Yes, we should drop ASM3 and the Java8 plugin as well and switch to ASM5.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2016-06-12 6:46 GMT+02:00 Johannes Geppert :
> Is there still any reason to still use asm3?
> Or should we change this with 2.5.x?
>
> Best Regards
>
> Johannes
> Am 11.06.2016 11:28 vorm. schrieb "Lukasz Lenart" :
>
>> 2016-06-10 19:22 GMT+02:00 Adam
Is there still any reason to still use asm3?
Or should we change this with 2.5.x?
Best Regards
Johannes
Am 11.06.2016 11:28 vorm. schrieb "Lukasz Lenart" :
> 2016-06-10 19:22 GMT+02:00 Adam Brin :
> > I’ll give it a try without the java8
5 matches
Mail list logo