[timtebeek]

• Fixes AddCommonAnnotationsDependencies triggers on JSR-305 (@Nullable) and adds redundant jakarta.annotation-api #1312

AddCommonAnnotationsDependencies added jakarta.annotation-api:1.3.x whenever anything under javax.annotation..* was used. That also matched JSR-305 types (javax.annotation.Nullable, Nonnull, CheckForNull, javax.annotation.concurrent.*) and the JDK's javax.annotation.processing.*. None of those are in jakarta.annotation-api, so the added dependency did nothing.

onlyIfUsing takes only one type pattern, so the single AddDependency is now one entry per JSR-250 type:

• javax.annotation.Generated, ManagedBean, PostConstruct, PreDestroy, Priority, Resource, Resources
• javax.annotation.security.*
• javax.annotation.sql.*

The Jakarta EE 9 AddJakartaAnnotationDependency keeps its broader pattern. Its tests expect javax.annotation.Nonnull to migrate to jakarta.annotation, which has Nonnull and Nullable since 2.1.

Tests:

• JSR-305 @Nullable and @ThreadSafe with jsr305 on the pom: the pom is unchanged. This test fails without the fix.
• @PostConstruct and @RolesAllowed used together: exactly one dependency is added.