Filelizer relies on filesystem access; consider adding ability to load from classpath

[jottinger]

The tests are full of "src/test/resource/" locations, mandated by loading using File, etc. This is non-idiomatic; consider adding support for reading from classpath instead, so you could load from "src/test/resource/something_multiple" and "/something_multiple", with the latter being more preferable for testing scenarios. (The filesystem call would be a fallback.)

[jottinger]

This is a pain to do, as it turns out: this was expected. (Spring and a few other frameworks have utilities to help, because it's a fairly common need but it's EXPENSIVE.) It's easy enough to DO, though: get the classloader, get the classpath from it, iterate over the resources in the classpath and look for matching resource names - you'd probably cache it on first scan so it's done once, and future requests would just iterate over the cache. But it IS potentially expensive (imagine a large project with spring boot and a bunch of other libraries).