Bug#646058: [librome-java] Missing OSGi metadata in jar manifest

[Jakub Adam]

Package: librome-java
Version: 1.0-2
Severity: normal

--- Please enter the report below this line. ---

Hello,

librome-java 1.0-1 supplied OSGi metadata inside jar META-INF/MANIFEST.MF. These additional
fields were removed at 1.0-2 because of bug #585578. As I'm packaging an Eclipse plugin that
has librome-java as its dependency and needs metadata for compilation, I'd like to get
them back.

I reproduced the invalid header field error described in #585578 and found out it was caused
by manifest fields with values longer than 72 bytes, that according to jar spec should be
split into multiple lines. In such cases jh_manifest added an extra line break immediately
after the attribute name, resulting in malformed manfest file.

After rebuilding the package with current version of javahelper in use, this bug occurs no
more, so I think there should be no problem with re-enabling insertion of the additional
fields into manifest.

Also I noticed that #585578 was fixed by removing jh_manifest from debian/rules, but it seems
current javahelper always calls jh_manifest in the build process, so the change has no effect
anymore. Because of this, rebuild of 1.0-2 package using the newest tools should be enough
to get OSGi metadata back to manifest.

Thank you in advance

Jakub

--- System information. ---
Architecture: amd64
Kernel:       Linux 3.0.0-1-amd64

Debian Release: wheezy/sid
   500 unstable        ftp.cz.debian.org
   500 unstable        emdebian.org
   500 testing         www.debian-multimedia.org
   500 testing         security.debian.org
   500 testing         ftp.cz.debian.org
     1 experimental    ftp.debian.org

--- Package information. ---
Depends            (Version) | Installed
============================-+-===========
libjdom1-java                | 1.1.1+dfsg-5


Package's Recommends field is empty.

Suggests              (Version) | Installed
===============================-+-===========
librome-java-doc      (= 1.0-3) |