Vojin Jovanovic

This item is now mostly complete when the `-H:ThrowMissingRegistrationErrors=` is set. To be complete it still depends on https://github.com/oracle/graal/issues/7487

I fully support the idea of the `module` field here. I would just not use the `"include"` at all. The `resources` with an array should signify that the file uses...

Those are great points! I would implement the basic glob patterns [from this article](https://en.wikipedia.org/wiki/Glob_(programming)). Easy to link and explain, not system-specific, easy to index, and fast at run time.

> Also since we have conditions, probably leaf nodes should store information about conditions for pattern that ends in that node? @vjovanov @olpaw Yes, we will have to check these...

Thank you greatly for the concise reproducer! Assigning it to @pejovica as he is providing support for AWT.

One of [our latest PRs](https://github.com/oracle/graal/pull/8872/files) should help with explaining what to do. We will also write a guide for this kind of cases for the next release. In this concrete...

The first error comes from the fact that the scanner pulled in native image classes. In later versions on GraalVM this should not happen. In the second snippet, the issue...

@selhagani for which example? Can you post an error?

I looked into this and it seems that `ClassGraph` does not see the classpath when it is scanning, however it can load all the classes with the correct class loader....

@zakkak the previous behavior can be kept with `-H:-ReportUnsupportedElementsAtRuntime` but I would not recommend that for end users. This mode should not ever affect the end users as they are...