Am 2019-02-23 um 00:40 schrieb Claude Brisson:
Hi all.
The VELOCITY-892 branch contains a fix for the corresponding issue [1].
The purpose is to let the method arguments conversion handler manipulate
the formal arguments types as java.lang.reflect.Type rather than
java.lang.Class, so that
I think upping the JDK version is good and healthy. Are there any worries
about JDK 1.8 changes in the Velocity code base? The main thing I have
seen get messed up in our code bases are routines that use Maps/Hashmaps
that expected things to be in the order added which changed in that jdk
+1 Java 8 has been around plenty long
On Fri, Feb 22, 2019 at 3:40 PM Claude Brisson
wrote:
> Hi all.
>
> The VELOCITY-892 branch contains a fix for the corresponding issue [1].
>
> The purpose is to let the method arguments conversion handler manipulate
> the formal arguments types as
Hi all.
The VELOCITY-892 branch contains a fix for the corresponding issue [1].
The purpose is to let the method arguments conversion handler manipulate
the formal arguments types as java.lang.reflect.Type rather than
java.lang.Class, so that when dealing with a method like
void foo(List
