Open bergmanngabor opened 2 months ago
Fixes #135
Huge thanks for asking for more tests! You made the right call - the more extensive test coverage revealed that the solution was not quite perfect, since there were serious underlying classloading problems as well (some related, some unrelated to inner classes or generic classes). This lead me down a rabbit hole that culminated in the introduction of a caching mechanism to the Java project based classloader.
(Note that what I have introduced is resource-based caching, so one classloader per vql file. If you can tell me how to have one shared classloader per source project rather than resource, I am all ears. Even better: can related projects have related classloaders?)
Fixes #125 as well.
The classes generated from this pattern now compile correctly:
(And the query results are correct as well)