Your message dated Sun, 07 Dec 2014 13:15:21 +0100
with message-id <>
and subject line Re: Bug#719094: generates broken Class-Path in MANIFEST.MF
has caused the Debian Bug report #719094,
regarding generates broken Class-Path in MANIFEST.MF
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
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 /usr/share/java/jar2.jar /usr/shar

Notice how it is automatically wrapped at approximately 70 characters? 
jh_manifest needs to generate an indented line for each JAR, e.g.

Class-Path: /usr/share/java/jar1.jar

As a work-around, I was able to insert spaces in the debian/manifest
file to make it wrap where I want it to, making it one very long line
with lots of spaces between each classpath entry

--- End Message ---
--- Begin Message ---
On Thu, 08 Aug 2013 18:35:38 +0200 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
> >
> Here is the package:
> It is currently in the NEW queue
> Could you have a look and tell me if I've used javahelper correctly or
> even try to build it the way you propose?

I am currently triaging bug reports for Javatools and had a look at this
one too. I can't reproduce any incorrect behaviour of jh_manifest and
the tool wraps the classpath in the manifest file correctly.

Here is an example how it works:

If all jar files are on the same line, jh_manifest will wrap them later
at 72 characters in the manifest file which is perfectly valid. There is
no need for additional spaces in avis.manifest.

As Emmanuel pointed out already, jh_classpath is another alternative
that allows to write the same information differently.

I am going to close this bug report as invalid now.



Attachment: signature.asc
Description: OpenPGP digital signature

--- End Message ---
This is the maintainer address of Debian's Java team
Please use for discussions and questions.

Reply via email to