JBossTools requires some method to discover from a non-running server which jars should be added to a project as exposed for clients (the project) to use. This should be a best-guess and does not need to be complete, but it's better if there is a way to determine which jars are public or private.

I'm not sure if this would be best addressed by jboss-modules, or some type of marker files (which it could be argued is a bad solution and we have too many such workarounds), or what.

Previous possible solutions introspected the xml files for each module to determine what jars / packages were public / private, but this was deemed unacceptable for reaching into a modules folder by ourselves.

Before that, we simply hard-coded which jars or folders to add for each app server version.

Requiring a running server violates our use case. Speed is of a high importance, and so therefore launching a new VM against a main class in jboss-modules is also not a great solution.