I've made my mod, it works well in my dev environment, however it has a lot of dependencies meaning that if it were to be used on another client, all of the required dependencies would have to be separately installed onto that client. Is there a method or tutorial for setting up gradlew so that when the mod is compiled, specified jars using their file path are embedded into the mod? I did see the forge dependencies page on github but I didn't see anything about embedding using a file path.

 

Also, in case it is necessary, I'm modding in 1.8. After I know how to do this, I'll port to 1.8.9.

 

EDIT: I am aware of licensing and will not embed anything that causes a breach of that dependencies license.

Embedding .jars is a bad idea.

 

What if the client already has the dependencies for other mods? Then their game will crash due to two different versions of the same mod.

It's best just to link to the dependencies on your mod webpage.

These dependencies aren't other forge mods but other projects made in java. However, I do understand what you mean and although I think it's unlikely that another mod will use those dependencies, I guess in the spirit of good coding practice, I'll just link them. Thanks.

 

To prevent conflicts you can use gradle's shadow/shade plugins.

But CPW added a simple hack for things like this:

https://github.com/MinecraftForge/MinecraftForge/commit/dc4dc55dcdcb86ec800f2a9170e468673046685b