Prevent generateMetadata
Profiles from generating GraalVM Reachability Metadata for arrays and JdkLogger
#36067
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For #29052 .
Changes proposed in this pull request:
generateMetadata
Profiles from generating GraalVM Reachability Metadata for arrays andJdkLogger
. According to [GR-44611] Tracing agent: seems like there is no way to ingore arrays oracle/graal#5900 , it is hard to say why GTA needs to collect this useless JSON. AndJdkLogger
isn't even a fully qualified class name that actually exists.com.oracle.svm.core.code.CodeCachePoolMXBean
. See the JavaDoc of https://github.com/oracle/graal/blob/vm-24.2.2/substratevm/src/com.oracle.svm.core/src/com/oracle/svm/core/code/CodeCachePoolMXBean.java and [GR-36063] [GR-45332] Fixes for SVM MemoryPool and MemoryManager MX beans. oracle/graal#6923 . It sounds like there is a bug in the buildArg of--exact-reachability-metadata
.BeanInfo
classes andCustomizer
classes.test
tointegration-test
#36050 where CI commands were not updated.Before committing this PR, I'm sure that I have checked the following options:
./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e
.