Consider binding provider implementation types using wildcard key (Bugzilla Bug 513442) #27
Labels
enhancement
New feature or request
Comments
mcculls
added
enhancement
cstamas
added a commit
that referenced
this issue
May 17, 2024
In short: now build works on both, Java 11 and Java 17 (tested with 11 and 17 Temurin on Linux). Similar to #61 and similarly, once this merged removal of Tycho is pending. Changes: * update GH workflow to use mvnw (instead of implicitly provided mvn by setup-java) * update wrapper to 3.2.0 and Maven to 3.9.1 * update all build plugins to their latest versions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue was created automatically with bugzilla2github
Bugzilla Bug 513442
Date: 2017-03-10 07:07:09 -0500
From: Stuart McCulloch <[email protected]>
To: Project Inbox <[email protected]>
Last updated: 2017-03-10 07:07:09 -0500
Comment 2812915
Date: 2017-03-10 07:07:09 -0500
From: Stuart McCulloch <[email protected]>
So provider implementations can be looked up by any of their superclasses/interfaces. Note this is different from looking up the type they provide, this is about locating the actual provider implementation itself. This is useful when the provider implements additional management interfaces.
The text was updated successfully, but these errors were encountered: