Bug#859001: libbrowserlauncher-java: No jar file without version number
Markus Koschany
apo at debian.org
Wed Mar 29 13:15:44 UTC 2017
Hi Ole,
Am 29.03.2017 um 14:56 schrieb Ole Streicher:
> Package: libbrowserlauncher-java
> Version: 1.3+dfsg-1
> Severity: serious
>
> The package contents are (mainly):
>
> /usr/share/java/BrowserLauncher2-1_3-1.3.jar
> /usr/share/java/BrowserLauncher2-1_3.jar -> BrowserLauncher2-1_3-1.3.jar
>
> There is no jar without a version number. This makes it impossible to
> add the jar to the CLASSPATH of other packages,
This is not true. You can add such jar files to your CLASSPATH.
> since the file name will
> change silently with the next version.
This is true.
> Therefore, please include also a versionless jar file
> BrowserLauncher2.jar. This is also requested by Java policy.
Java Policy is more like Parley from Pirates of the Caribbean and
incomplete by the way. I suggest to downgrade the bug to "important"
because it does not affect jmodeltest, the only reverse-dependency at
the moment and a missing symlink is not release critical in this case
and can be trivially worked around.
Regards,
Markus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20170329/5e0ee1d7/attachment.sig>
More information about the pkg-java-maintainers
mailing list