I want to use dependencies used in the client but there are conflicts. Suggestions?

[boomslap 5]

I would like to use the StringUtils class from the apache.commons.lang3 package on my script. I have added it as a dependency on my maven pom file but since the same package exists inside the client.jar, it gets priority during runtime and I get a 'NoSuchMethodError' when executing for instance the StringUtils.capitalize(String) method because that method doesn't exist in the version included in the client.jar.

Is there a workaround this to give priority to my dependency over the package included in the client.jar?

Could you possibly include the entire library inside the client.jar?

Thanks!

 

[Axolotl 31]

5 hours ago, boomslap said:

I would like to use the StringUtils class from the apache.commons.lang3 package on my script. I have added it as a dependency on my maven pom file but since the same package exists inside the client.jar, it gets priority during runtime and I get a 'NoSuchMethodError' when executing for instance the StringUtils.capitalize(String) method because that method doesn't exist in the version included in the client.jar.

Is there a workaround this to give priority to my dependency over the package included in the client.jar?

Could you possibly include the entire library inside the client.jar?

Thanks!

 

Not too sure on the overall answer with dependancy priority when it comes to naming conflicts, but when it comes to StringUtils.capitalize heres my GUI failsafe you can use:
 

private static String itemNameFormatting(String itemName)
{
    StringBuilder formatted = new StringBuilder();
    String lower = itemName.toLowerCase();
    boolean upperCase = true;
    for(int i = 0; i < lower.length(); i++)
    {
        char letter = lower.charAt(i);
        if(upperCase)
        {
            String upper = "" + letter;
            formatted.append(upper.toUpperCase());
            upperCase = false;
        }
        else
            formatted.append(letter);
    }
    MethodProvider.log("Formatted itemName: " + itemName + " to: " + formatted);
    return formatted.toString();
}

[boomslap 5]

4 hours ago, Axolotl said:

Not too sure on the overall answer with dependancy priority when it comes to naming conflicts, but when it comes to StringUtils.capitalize heres my GUI failsafe you can use:
 

private static String itemNameFormatting(String itemName)
{
    StringBuilder formatted = new StringBuilder();
    String lower = itemName.toLowerCase();
    boolean upperCase = true;
    for(int i = 0; i < lower.length(); i++)
    {
        char letter = lower.charAt(i);
        if(upperCase)
        {
            String upper = "" + letter;
            formatted.append(upper.toUpperCase());
            upperCase = false;
        }
        else
            formatted.append(letter);
    }
    MethodProvider.log("Formatted itemName: " + itemName + " to: " + formatted);
    return formatted.toString();
}

Thanks a lot for the suggestion and the code! Recreating the functions I need is something I thought of doing but I would want to avoid it if possible since this is an issue where similar conflicts can happen with other dependencies and they are quite annoying to find and fix.

[NotAnyChef 0]

I'm in the same boat