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

Daniel Pocock daniel at pocock.com.au
Thu Aug 8 13:49:13 UTC 2013


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 longer than 72 bytes (not characters), in its
>>> UTF8-encoded form. If a value would make the initial line longer than
>>> this, it should be continued on extra lines (each starting with a single
>>> SPACE)."
>>>
>>
>> I tried doing that in debian/manifest, but it still didn't work, they
>> were just joined together again
>>
>> Can you give an example of how debian/manifest should be written?
>>
>> [...]
> jh_manifest will wrap the lines unconditionally.  But that is not the
> issue.  The class path entry generated:
>
> """
> Class-Path: /usr/share/java/jar1.jar /usr/share/java/jar2.jar /usr/shar
>  e/java/jar3.jar
> """
>
> is perfectly legal and to my knowledge correct (which I believe was the
> point Emmanuel was trying to make).  The above will unwrap to (the eqv. of):
>
> Class-Path: /usr/share/java/jar1.jar /usr/share/java/jar2.jar
>  /usr/share/java/jar3.jar

Just to clarify: you are suggesting that I should manually break the
lines in debian/manifest at 72 characters and then the JVM will
concatenate them back together again at runtime?



More information about the pkg-java-maintainers mailing list