External Jar error while using default scope(compile) for dependencies on Saviynt 23.4

[Harikrishnan]

Hi All,

We use external Jar functionality in our production which uses an older version of Saviynt. So, we have been testing the new version of Saviynt(23.4) in our dev environment and noticed that the external Jar file throws no class error for dependencies with default scope(compile). However, the Jar dependencies with default scope work perfectly on the older version. Any fix or solution for this?

Thanks,

Hari

[nimitdave]

From where are you invoking the external jar. Did it never work in EIC version.

To isolate the issue try with simple jar 2 logger statements. Entry and exit in the method.

Also please note that system.out.println is deprecated from 23.4 and later version. 

[Harikrishnan]

I am using an external JAR job to run the JAR. The issue is that the JAR depends on GSON, which is already packed within the JAR file with the help of the Maven assembly plugin. However, when the JAR is invoked, the logs show that GSON class is undefined. We use the same JAR which is there in production. But we get the class error in the dev EIC version(23.4)

[nimitdave]

Please create a support ticket with logs working and issue one. Also the jar.