Aggregating Dependent Module Resources Before Jar-ring?

Is there a decent way to aggregate resources based on dependencies to a module?

I’ve racked my brains on this one and done a lot of googling to boot, but everything seems pretty locked down short of getting the jars and extracting known resources from that (perhaps by making sure they all end up in a subdirectory). This seems kind of dirty (could be very costly) and that I should be able to know the resource directories of dependencies before a jar is generated.

Use case is having a library that has an asset packer tool being used in a consuming side-by-side project. The jvm module of this consuming project needs to be able to run all of the assets found in resource folders in dependent modules through the asset packer. It then generates a json files manifest of all the resources for the resulting application to index and improve file access at runtime.