-
We use micronaut-platform as our targeted bom. There hasn't been a release since Feb. and we need a fix for #11598 . We saw some comments in some discussions/tickets about leveraging the latest micronaut-core release when an up-to-date micronaut-platform is not yet available. In doing so, when compiling even a minimal project that uses only micronaut-core and micronaut-test, we see some annotation processing issue:
Maybe we have our versions miswired, but it is difficult to know what the problem is.
We have a parent pom that contains the following versions:
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
the fix was included in 4.7.17 so you can update to that version |
Beta Was this translation helpful? Give feedback.
-
@graemerocher We upgraded to micronaut platform 4.8.0 (which uses core 4.8.9) and we still see this compilation error on an inert project that just pulls in micronaut core and micronaut test (for the @MicronautTest annotation and Junit5 integration). Is that expected? It looks like micronaut test 4.7.0 was based upon micronaut core 4.8.0. Can this cause this issue?
|
Beta Was this translation helpful? Give feedback.
-
Looks like the micronaut-validation annotation processor is the culprit here. Adding io.micronaut.validation:micronaut-validation-processor:4.9.0 to the annotation processors causes this compilation error. |
Beta Was this translation helpful? Give feedback.
-
I noticed that if we switch our project to use micronaut-parent as the parent (pom) then the issue is resolved. The key appears to relate to this, in the micronaut-parent maven compiler settings:
.... with the above line included, the compiler issue is no longer reproducible. |
Beta Was this translation helpful? Give feedback.
I noticed that if we switch our project to use micronaut-parent as the parent (pom) then the issue is resolved. The key appears to relate to this, in the micronaut-parent maven compiler settings:
<annotationProcessorPathsUseDepMgmt>true</annotationProcessorPathsUseDepMgmt>
.... with the above line included, the compiler issue is no longer reproducible.