Skip to content
This repository has been archived by the owner on Feb 23, 2023. It is now read-only.

Automatic nested condition handling doesn't work when conditions are at the method level #855

Closed
aclement opened this issue Jun 22, 2021 · 0 comments
Assignees
Labels
type: compatibility Native image compatibility issue
Milestone

Comments

@aclement
Copy link
Contributor

The analysis system can handle this:

    @Conditional(Foo.class)

and recognize that the referenced condition class extends AbstractNestedCondition so contains subtypes that may have further conditions on them:

class Foo extends AllNestedConditions {

    @ConditionalOnProperty(name="something")
    static class FirstPropCheckCondition { }

    @ConditionalOnProperty(name="something")
    static class SecondPropCheckCondition { }

}

In this case it should automatically register (for reflective/resource access) the subclasses inside Foo.

However, it currently only recognizes this pattern if used at the type level, not at the method level.

@aclement aclement added the type: compatibility Native image compatibility issue label Jun 22, 2021
@aclement aclement added this to the 0.10.1 milestone Jun 22, 2021
@aclement aclement self-assigned this Jun 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: compatibility Native image compatibility issue
Development

No branches or pull requests

1 participant