If you are packaging a library, this warning is safe to be ignored. If you are packaging a Java program, I would suggest putting the Class-Path in a separate file (e.g. `/usr/share/sbt.classpath`) and read it in the launcher script via `java -cp`.
if the Java program has its own JAR loading mechanism (e.g. Gradle), you can still just ignore the warning. Cheers, Kai-Chung Yan 2017-02-28 21:56 GMT+08:00 Emmanuel Bourg <[email protected]>: > Hi Frederic, > > Le 27/02/2017 à 15:53, Frederic Bonnard a écrit : > >> I understand that I should provide the list of jars upon which >> libsbt-serialization-java will depend on at runtime. >> Is my understanding right ? > > This is correct. > >> How do you handle this ? : >> - should I list all jars in libjson4s-java, libjawn-java and >> libscala-pickling-java ? > > Only the direct dependencies should be listed, not the transitive ones. > >> - may I run strace and see which jars are loaded ? >> Anything tips on how you deal with that ? > > You can ignore this warning, it isn't very important and arguably flawed > for various reasons. > > Emmanuel Bourg >
