Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
Package: javahelper Version: 0.43 Severity: important I've tried listing my classpath JARs in both debian/manifest and in debian/rules (export CLASSPATH) Either way, the generated MANIFEST.MF is broken, because of the line wrapping issue, e.g. I have Class-Path: /usr/share/java/jar1.jar

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Emmanuel Bourg
Manifest files support wrapped values, see: http://docs.oracle.com/javase/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
On 08/08/13 15:08, Emmanuel Bourg wrote: Manifest files support wrapped values, see: http://docs.oracle.com/javase/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Niels Thykier
On 2013-08-08 15:15, Daniel Pocock wrote: On 08/08/13 15:08, Emmanuel Bourg wrote: Manifest files support wrapped values, see: http://docs.oracle.com/javase/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files No line may be longer than 72 bytes (not characters), in

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
On 08/08/13 15:47, Niels Thykier wrote: On 2013-08-08 15:15, Daniel Pocock wrote: On 08/08/13 15:08, Emmanuel Bourg wrote: Manifest files support wrapped values, see: http://docs.oracle.com/javase/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files No line may be

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Niels Thykier
On 2013-08-08 15:49, Daniel Pocock wrote: [...] Just to clarify: you are suggesting that I should manually break the lines in debian/manifest at 72 characters No, jh_manifest will do that for you - whether you like it or not. and then the JVM will concatenate them back together again at

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
On 08/08/13 15:59, Niels Thykier wrote: On 2013-08-08 15:49, Daniel Pocock wrote: [...] Just to clarify: you are suggesting that I should manually break the lines in debian/manifest at 72 characters No, jh_manifest will do that for you - whether you like it or not. and then the JVM will

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
On 08/08/13 16:43, Emmanuel Bourg wrote: If you just want to set the classpath I suggest using jh_classpath instead. The debian/package.classpath file contains one line per jar and you don't have to care about the length of the lines: usr/share/java/foo.jar jar1.jar jar2.jar jar3.jar

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Emmanuel Bourg
If you just want to set the classpath I suggest using jh_classpath instead. The debian/package.classpath file contains one line per jar and you don't have to care about the length of the lines: usr/share/java/foo.jar jar1.jar jar2.jar jar3.jar __ This is the maintainer address of Debian's