Upgrade to ExtVal r3
Using ExtVal r3 in existing Applications
@Length and @Pattern won't validate empty values any more. That means previous versions of ExtVal perform an implicit required validation in some cases. With ExtVal r3 you don't see these implicit validations any more.
If you are fine with these implicit validations, you have several possibilities to get back to the original behavior:
Provide a custom validation strategy for these constraints and annotate them with @EmptyValueAwareValidationStrategy.
Use the approach described by Rudy in EXTVAL-82
Custom Validation Strategies
Fixed typo - see AbstractAnnotationValidationStrategy#getValidationErrorFacesMessage
CrossValidationStorageEntry moved to the package org.apache.myfaces.extensions.validator.crossval.storage
- The behavior is the same - so you just have to fix the import statements.
If an add-on extends a class which isn't marked as UsageCategory.API, it's possible that there are some changes. e.g. ValidationInterceptorWithSkipValidationSupport was renamed to: PropertyValidationModuleValidationInterceptor Please write to the dev list if you face any issue.