You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Currently, com.hazelcast:hazelcast:5.2.1 and org.ehcache:ehcache:3.10.8-jakarta are both in the nativeTest process, and a part of javax.cache:cache-api:1.1.1 GraalVM reachability metadata is manually maintained dependent. It should be expected behavior to supplement this API facade library with more specific GraalVM reachability metadata.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Considering that javax.cache:cache-api:1.1.1 itself is just a set of interfaces, writing tests for it seems like a hassle.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
com.hazelcast:hazelcast:5.2.1
#122org.ehcache:ehcache:3.10.8-jakarta
#124Describe the solution you'd like
A clear and concise description of what you want to happen.
com.hazelcast:hazelcast:5.2.1
andorg.ehcache:ehcache:3.10.8-jakarta
are both in the nativeTest process, and a part ofjavax.cache:cache-api:1.1.1
GraalVM reachability metadata is manually maintained dependent. It should be expected behavior to supplement this API facade library with more specific GraalVM reachability metadata.Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
javax.cache:cache-api:1.1.1
itself is just a set of interfaces, writing tests for it seems like a hassle.Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: