(Some Java code style changes for new code.)
(Version history fixes)
Wrong overloaded error message fixes.
(Source code formatting fix)
(Some new test cases for overloaded method handling)
Array-to-List conversion for overloaded methods (with 2.3.21 incompatible improvement on): FTL sequence values that wrapped a Java array (when FreeMarker was also aware of that via AdapterTemplateModel or WrapperTemplateModel) were not seen as applicable to a parameter with List type if there were multiple overloaded methods with the same number of parameters but with different types on the position of the array parameter. So this is pretty much like the issue described in the previous point, but for array to List conversion. The array to List conversion will be avoided if possible, but it will be attempted if there's no other alternative. Note that unlike with List to array conversions, here FreeMarker can't cope with multi-dimensional lists, that is, an array-of-arrays won't be converted to a List-of-List-s.
(A useless catch block removed)
Bug fixed [411]: Invalid execution environment names were fixed: J2SE-1.6 to Java2SE-1.6, J2SE-1.7 to JavaSE-1.7. Also, J2SE-1.8 was removed for now, as we don't utilize any features in it dynamically (to prevent misunderstandings, Java 8 is still supported).
(Few more tests)
More consistent (slightly fixed) method and constructor invocation error messages (also moved MethodUtils under f.e.beans). Also improved _ErrorDescriptionBuilder a bit.
(Eclipse: Organize import when saving)
(Some internal javadoc and import reorg.)
Started generalizing numerical type flags to a more generic type flags that can carry extra information for unwrapping before overloaded method calls. Right now the flags are filled, but not used anywhere.
(Added missing log4j.properties to the test suite)
Fixes and improvements in method call error messages
(Prevent JUnit warning under Eclipse.)
Unwrapping for overloaded methods now utilizes the recently introduced typeFlags to avoid unwrapping multi-typed FTL values to the wrong Java type. (Also 0 parameter methods won't have null TypeFlags anymore. Also fixed the precondition that allowed unwrapping to List on parameter positions where an array type occurs.)
(Some more typeFlags tests)
(Added typeFlags to the version history.)
FTL string to Java char/Character conversion now works for overloaded method parameters; earlier it has worked for non-overloaded methods only. If the string length is 1, it will be seen as compatible with parameters with char or Character type.