graalvm Improvements to the way metadata is generated,Metadata is generated by the class name directory, which makes it easy to troubleshoot missing metadata

[yangzehan]

For example, org.ssssssss.magicapi.modules.db.cache.SqlCache can generate the org.ssssssss.magicapi.modules.db.cache directory in the output directory and create a metadata file containing all classes under the org.ssssssss.magicapi.modules.db.cache path in a single directory file.Will this be more conducive to troubleshooting

[selhagani]

Hi @yangzehan,

Thank you for the suggestion. While the idea of consolidating metadata into a single file for easier troubleshooting seems helpful at first glance, it isn't quite practical in this case. The metadata generated by GraalVM reflects multiple aspects, such as reflection, JNI, and other runtime components, which are inherently separate. Merging all of these into one file could make the metadata harder to parse and understand, as it would obscure the distinctions between these different elements.

In addition, GraalVM's current approach of organizing metadata by class directory provides clarity by maintaining these distinctions, which is essential for efficient debugging and troubleshooting.

I hope this clarifies why such a change may not be feasible. However, we're always open to further suggestions and discussions!