-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
access-filter.json excludes most, but not all files when using a descendants pattern #3174
Comments
@helpermethod thanks for reporting the issue |
@helpermethod I tried my side and it worked |
@helpermethod please share the graalvm version you are using |
@mcraj017 Sorry I've accidentally re-added I'm using GraalVM CE 21.0.0 with Java 11. |
Hi @mcraj017! I've moved the broken status into its own branch, to be able to move forward with main https://github.com/helpermethod/connect-offset-reset/tree/access-filter |
@helpermethod I pulled the latest changes from the repo and still able to build successfully |
@mcraj017 Do you use the latest releases version, of do you use GraalVMs current |
@helpermethod I am using GraalVM 21.0 java 11 |
@helpermethod did you tried with GraalVM 21.0 java 11? |
Closing the issue as user did not respond in the last month |
Describe the issue
For driving the generation of
reflect-config.json
et al I'm using the tracing agent in combination with JUnit and TestContainers. In order to not include test-related classes, I've added the followingaccess-filter.json
file:The excludes work well, except for the
"excludeClasses": "com.github.dockerjava.**"
.While it excludes most of the files and directories under
com.github.dockerjava
, it doesn't excludecom.github.dockerjava.api.model.Bind
which shows up in the generatedreflect-config.json
:This leads to failing the
native-image-build
because theBind
class is obviously not found (being not part of the CP).Steps to reproduce the issue
Describe GraalVM and your environment:
More details
Verbose
native-image-maven-plugin
log outputThe text was updated successfully, but these errors were encountered: