Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Use case: Let's assume your main artifact is a "plugin" of some sort. Moreover, assume that the "host" of your plugin uses SLF4J API for logging, hence the module have slf4j-api declared as compile dependency (or provided, does not matter). Still, you want to create a self contained JAR out of same module, hence shade it. But the problem is given: how would standalone JAR log?
You should be able to "inject" extra JARs, but at the same time to have all the "benefits" of all resource transformers as well (ie. your "extra artifact" may have Sisu components, or Service providers).
The extrajars IT showcase this very scenario.