Quoting Emmanuel Bourg: > Package: lintian > Version: 2.114.0 > Severity: normal > > The bad-jar-name check flags many packages that do conform to the Java policy, > which allows a suffix after the base package name (packagename-extraname.jar). > > See for example the batik package, /usr/share/java/batik-all.jar and its > siblings are wrongly reported.
The policy here [1] says: | Their classes must be in jar archive(s) in the directory /usr/share/java, with the name packagename[-extraname]-fullversion.jar. | The extraname is optional and used internally within the package to separate the different jars provided by the package. | The fullversion is the version of that jar file. In some cases that is not the same as the package version. How does `batik-all.jar` conform to that? [1] https://www.debian.org/doc/packaging-manuals/java-policy/ch02.html#policy-libraries Best, Nilesh
