Bug#745815: libjarjar-java: generate jars with invalid information

[Miguel Landaeta]

On Fri, Apr 25, 2014 at 04:10:25PM +0200, Emmanuel Bourg wrote:
> I compared the dgminfo files from groovy-all.jar in stable and unstable,
> in unstable the 0x0D bytes have been replaced by 0x0A. It looks like the
> file was erroneously processed as a text file and the line terminators
> were transformed.
> 
> I fail to see what change in jarjar 1.4 caused this though.

Thanks for the info Emmanuel. I'm also trying to review the changes
and see if/how I can make jarjar function like it did 1.1 for groovy.

I thought I could work around this in gradle by using groovy jar
instead of groovy-all one but this doesn't work because that tool depends
closely on -all.jar.

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at
http://db.debian.org/fetchkey.cgi?fingerprint=4CB7FE1E280ECC90F29A597E6E608B637D8967E9
"Faith means not wanting to know what is true." -- Nietzsche
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20140425/8091b3ec/attachment.sig>