Understand lifecycle of branch vs release

[tchiotludo]

Hi,

I'm heavily use the Micronaut Validation for my internal usage.

I've an NullPointerException on micronaut 2.2.
Looking deeply to understand it's failed here :

micronaut-core/validation/src/main/java/io/micronaut/validation/validator/DefaultValidator.java

Lines 1322 to 1329 in 8d8e1b6

	final BeanIntrospection<Object> beanIntrospection = getBeanIntrospection(propertyValue);
	AnnotationMetadata annotationMetadata = cascadeProperty.getAnnotationMetadata();
	if (beanIntrospection == null && !annotationMetadata.hasStereotype(Constraint.class)) {
	// error: only has @Valid but the propertyValue class is not @Introspected
	overallViolations.add(createIntrospectionConstraintViolation(
	rootClass, rootBean, context, propertyValue.getClass(), propertyValue));
	return;
	}

because propertyValue == null.

I checked the master branch,

micronaut-core/validation/src/main/java/io/micronaut/validation/validator/DefaultValidator.java

Line 1322 in e07d7c3

private <T> void cascadeToOne(

The method is completely rewrite, and I see a unit test that cover must my failed cases, Nice !

Looking at the blame :
https://github.com/micronaut-projects/micronaut-core/blame/master/validation/src/main/java/io/micronaut/validation/validator/DefaultValidator.java#L1336

@graemerocher fix that 2 years ago, and the modification is not on the any release branch.

How to handle the inclusion from master to release branch ?
Is there any ETA on this modification on release ?
Maybe it's a BC fix, I don't know, just seems weird that a commit 2 years ago was not released.

Thanks

[graemerocher]

Could just be a regression from the changes. Your issue has been assigned to a milestone. We currently release patch releases every 1-2 weeks and minor releases every 6 weeks (the next minor release is 2.3) so it won't be long before your fix is included I imagine.

[tchiotludo]

Thanks for the prompt reply !
You seems to have quickly found the information for the next milestone, I can't find the path to the issue.
But glad to know it will come quickly :)

[graemerocher]

Ah actually I thought this was #4590

Could you create another issue to track your NPE?

[tchiotludo]

No, it's another one, moving a large codebase from micronaut 1.3.7 to 2.2, so I discover a lot of issues at the same time 😄

Done here : #4593

Thanks