[1.12.2] Add Baubles as Dependency

[Seynox]

Hello!

Im trying to get Baubles as a dependency, i already tried so i have the bauble api in my workspace, and the mod installed when i launch with Eclipse (I didnt manually downloaded Bauble, it installed itself after adding few things in my build.gradle (see below)) so i thought that was it, but when i build my mod and i add it to my minecraft, it's not installing Bauble by itself so i have to do it myself (I put Baubles in the mod folder with my mod).

Is there a way to have the Bauble mod automatically installed?

 

The things i added to build.gradle :

Spoiler

repositories {
    
    maven { url 'https://jitpack.io' }
}

dependencies {
    
    deobfCompile "com.github.azanor:Baubles:${baubles_version}"

}

 

 

[Seynox]

Anyone?

[DavidM]

23 hours ago, Seynox said:

Is there a way to have the Bauble mod automatically installed?

No. The player have to manually install such dependencies.

 

Well, technically you could auto download dependencies (like how CodeChicken Core/Lib is installed on Minecraft launch); however, such method is disapproved (partly because its downloading files without the player's permission) and should not be attempted.

Edited May 5, 2019 by DavidM

[Cadiboo]

On 5/5/2019 at 10:55 PM, DavidM said:

Well, technically you could auto download dependencies (like how CodeChicken Core/Lib is installed on Minecraft launch); however, such method is disapproved (partly because its downloading files without the player's permission) and should not be attempted.

Don’t do this. If you have permission from the author you can use Forges Jar-In-Jar system to put baubles inside your mod.

[desht]

9 hours ago, Cadiboo said:

Don’t do this. If you have permission from the author you can use Forges Jar-In-Jar system to put baubles inside your mod.

Even that is horrible. OP, just list Baubles as a required dependency on your mod and be done with it. Ensuring that the right dependencies are present for your mod is a job for modpack authors, not mod developers.

[desht]

4 hours ago, diesieben07 said:

No, it's not, at least if it's natively supported by the mod being depended on (aka they have the Maven-Artifact manifest attribute). If that is the case, Forge will resolve the dependencies properly and only set up one version of the dependency, or report an error if there are version conflicts (I think).

Fair enough. Still makes me uneasy though... I've had too many experiences with dependency hell in the past, Forge or otherwise