False positive missing @Executable(processOnStartup = true) warning

[auloin]

While upgrading JobRunr's Micronaut Integration to Micronaut 5, I get the following warning:

WARN  i.m.context.DefaultBeanContext - org.jobrunr.micronaut.autoconfigure.RecurringMethodProcessor: ExecutableMethodProcessor is supposed to be used with an annotation that has @Executable(processOnStartup = true). In the future version this will be an error.

Our use case include a Recurring annotation that's imported from a non Micronaut project, so we use Micronaut's TypedAnnotationMapper to map it to an annotation with the processOnStartup = true flag.

For the detailed implementation:

• RecurringMethodProcessor: https://github.com/jobrunr/jobrunr/blob/master/framework-support/jobrunr-micronaut-feature/jobrunr-micronaut/src/main/java/org/jobrunr/micronaut/autoconfigure/RecurringMethodProcessor.java
• RecurringAnnotationMapper: https://github.com/jobrunr/jobrunr/blob/master/framework-support/jobrunr-micronaut-feature/jobrunr-micronaut-annotations/src/main/java/org/jobrunr/micronaut/annotations/RecurringAnnotationMapper.java

Do we need to change our approach? Any suggestions? Or is this a false positive?

Thanks for the help!

[lMysticl]

This looks like a false positive in the new validation, although it will need to be addressed before the warning becomes an error.

The validator currently takes the A type argument from ExecutableMethodProcessor<A> and inspects the annotation class itself:

ClassElement annotation = processor.get("A");
AnnotationValue<Executable> executable =
        annotation.getAnnotation(Executable.class);

See DeclaredBeanElementCreator.

Your TypedAnnotationMapper adds @Executable(processOnStartup = true) to the metadata of each use of @Recurring, but the check above only examines the declaration of org.jobrunr.jobs.annotations.Recurring. It does not consult the mapped metadata. Because that annotation is intentionally framework-neutral, it cannot directly carry a Micronaut annotation.

BeanDefinitionProcessor is not an equivalent replacement here: it processes bean-level annotations, while this use case needs to discover individual recurring methods at startup. The Micronaut 5 migration note also says that startup method processing remains the intended ExecutableMethodProcessor use case.

A local bridge annotation should avoid the warning without adding Micronaut to JobRunr's core annotation:

@Target(ElementType.METHOD)
@Retention(RetentionPolicy.RUNTIME)
@Executable(processOnStartup = true)
@interface MicronautRecurring {
}

The typed mapper can return both values:

return List.of(
        annotation,
        AnnotationValue.builder(MicronautRecurring.class).build()
);

and the processor can use:

ExecutableMethodProcessor<MicronautRecurring>

Keeping the original Recurring annotation value allows JobRunrRecurringJobScheduler to continue reading id, cron, interval, and zoneId. I would add an integration test that asserts both annotations are present on the executable method and that a recurring job is scheduled before adopting this workaround.

Longer term, I think this is worth reporting in Micronaut: the validation should either account for TypedAnnotationMapper output or provide a supported way for a framework-neutral external annotation to satisfy the startup-processing contract.

The relevant Micronaut 5 migration note is here.