We need some way to store dependencies in plugins.
May be 'lib' directory, like in WAR?
XakepSDK
All 5 comments
The Gradle shadow plugin and the Maven shade plugin are the recommended ways of doing this, and don鈥檛 need any special support.
JBYoshi
on 27 Sep 2017
The best way to make a dependency trash from your plugin jar.
upd: Plugins are not isolated from each other, some plugin can provide lib-a:1.0.0 and another plugin can provide lib-a:0.9.8. Need a way to handle this too.
XakepSDK
on 27 Sep 2017
@XakepSDK That's why you should relocate (e.g. move their classes into a subpackage of your plugin) the dependencies you shade into your plugins. That way they have different class names and won't conflict with each other.
Minecrell
on 27 Sep 2017
Closing as SpongeAPI isn't going to reinvent the wheel that modern toolchains already do much better than we ever would.
Zidane
on 27 Sep 2017
I should also point out that if running on Forge the requested functionality is already fully supported via the ContainedDeps manifest entry.
Mumfrey
on 28 Sep 2017
Related issues
Eufranio
路
4Comments
Grinch
路
4Comments
gabizou
路
5Comments
XakepSDK
路
5Comments
TBlueF
路
5Comments
Most helpful comment
@XakepSDK That's why you should relocate (e.g. move their classes into a subpackage of your plugin) the dependencies you shade into your plugins. That way they have different class names and won't conflict with each other.