Sam Kruglov

Sure, don’t bother with credits, I just added a dependency :)

you could also have a master branch with N commits instead of N branches. That way you can still walk through the steps using git hard reset but you can...

Any plans for this? I prefer using `PER_CLASS` but it seems mockito for some reason recreates all `@Mock` fields before each test still while leaving `@InjectMocks` unchanged. ```java @ExtendWith(MockitoExtension.class) class...

> Unable to decrypt Maven password using PlexusCipher org.sonatype.plexus.components.cipher.PlexusCipherException: java.lang.ArrayIndexOutOfBoundsException (c) CI

Also worth mentioning. `ResponseEntityExceptionHandler` has handlers for both `BindException` and for `MethodArgumentNotValidException` which also extends `BindException` since the related issue was fixed. The handlers are identical, so we can remove...

I found one more thing, that during handling of `ConstraintViolationException` I actually must take a look into the class it originated from (`e.constraintViolations[*].rootBeanClass`) to see if that is a `Controller`...

And one more: `org.springframework.http.converter.HttpMessageNotReadableException` may contain deserialization errors, which may also be client errors. In case of Jackson, I need to catch `HttpMessageNotReadableException` and check if it has a cause...

And one more: `org.springframework.beans.TypeMismatchException` doesn't have `propertyName` initialized even though it's subtype knows it, just doesn't call `initPropertyName()`.

Also `MissingServletRequestParameterException` does not have a proper access to the parameter type (`getParameterType` is a `String`) unlike `MissingPathVariableException` which does. I need it to detect if the "missing variable" is...

@ascopes thanks for your input! I kind of agree that `ConstraintViolationException` should be a server error. The reason is that you can annotate any `@Component` with `@Validated` and validate method...