Re: About manifest's Class-Path

2017-02-28 Thread Markus Koschany
Am 28.02.2017 um 14:56 schrieb Emmanuel Bourg: [...] > You can ignore this warning, it isn't very important and arguably flawed > for various reasons. Shall I file a bug report against Lintian to remove it? Or can this warning be improved somehow? Most people seem to ignore it at the moment. Rega

Re: About manifest's Class-Path

2017-02-28 Thread 殷啟聰
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 mecha

Re: About manifest's Class-Path

2017-02-28 Thread Emmanuel Bourg
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

About manifest's Class-Path

2017-02-27 Thread Frederic Bonnard
Hi, I'm trying to fix a lintian which is the following : W: libsbt-serialization-java: missing-classpath libjson4s-java, libjawn-java, libscala-pickling-java N: N:None of the jar files contained in the package declare a Class-Path in N:their manifest, but the package depends on at least