1.11.1 #259
MaisiKoleni
announced in
Releases
1.11.1
#259
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
User-Side Changes
DynamicField
. (see Do not ignore cases for attribute names #258, credits to @JohannesStoehr)The likely default that users want is that the field names are used as-is, so the case-insensitive default is counterintuitive and can lead to problems if constants and instance variables share the same name but in different capitalization.
ReflectionTestUtils
if a member is inaccessible because of the visibility of its containing class and not the member's own modifiers. (see ReflectionTestUtils: Improve Feedback if classes are not public #254, credits to @Strohgelaender)The failure message now distinguishes the different problem sources and will tell the students whether the problem is the class or the attribute/method/constructor.
ReflectionTestUtils
now offers the methodssetValueOfAttribute
andsetValueOfNonPublicAttribute
to set the value of attributes. The modification of final fields is prohibited. (see ReflectionTestUtils: Methods for changing values of attributes #256)ReflectionTestUtils
now offers re-throwing methods for instance creation to allow testing of exceptions thrown in constructors. (see ReflectionTestUtils: Testing exceptions in constructors #257)DynamicField
now offers methods to set field values for static and instance fields. The modification of final fields is prohibited.1.4.4
to1.4.5
. See their release notes for details.Developer-Side Changes
ReflectionTestUtils
and the Dynamics Frameworkspotless-maven-plugin
This discussion was created from the release 1.11.1.
Beta Was this translation helpful? Give feedback.
All reactions