Path: csiph.com!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!bofh.it!news.nic.it!robomod
From: Markus Koschany <apo@debian.org>
Newsgroups: linux.debian.maint.java
Subject: Re: maven-*-helper JAR placement seems to contradict Java policy
Date: Fri, 15 Oct 2021 13:40:02 +0200
Message-ID: <D8tJ8-HY-13@gated-at.bofh.it>
References: <D8s0G-80J-5@gated-at.bofh.it>
Old-Return-Path: <apo@debian.org>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-WWu1/TyuruAhxvxDeZFM"
MIME-Version: 1.0
Approved: robomod@news.nic.it
Lines: 77
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.java:12304


--=-WWu1/TyuruAhxvxDeZFM
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello,

Am Freitag, dem 15.10.2021 um 12:41 +0300 schrieb Andrius Merkys:
> Hello,
>=20
> Java policy on Java libraries (Ch. 2.4.) reads [1]:
>=20
> =C2=A0=C2=A0=C2=A0 Their classes must be in jar archive(s) in the directo=
ry /usr/
> =C2=A0=C2=A0=C2=A0 share/java, with the name packagename[-extraname]
> =C2=A0=C2=A0=C2=A0 -fullversion.jar. The extraname is optional and used i=
nternally
> =C2=A0=C2=A0=C2=A0 within the package to separate the different jars prov=
ided by the
> =C2=A0=C2=A0=C2=A0 package. The fullversion is the version of that jar fi=
le. In some
> =C2=A0=C2=A0=C2=A0 cases that is not the same as the package version.
>=20
> =C2=A0=C2=A0=C2=A0 Some package must also provide a symbolic link from
> =C2=A0=C2=A0=C2=A0 packagename-extraname.jar to the most compatible versi=
on of the
> =C2=A0=C2=A0=C2=A0 available packagename-extraname-version.jar files.
>=20
> However, it seems that packages built with maven-{debian,repo}-helper
> default settings contain the opposite: JAR archives are named
> packagename-extraname.jar, and packagename-extraname-version.jar are
> symbolic links to packagename-extraname.jar. For example see
> libcommons-lang3-java.
>=20
> This looks like a contradiction to me. Or am I just misreading the policy=
?
>=20
> [1] /usr/share/doc/java-policy/debian-java-policy.txt.gz, java-policy 0.5=
7

Indeed, that looks like a bug in libcommons-lang3-java or rather maven-debi=
an-
helper to me. I have just checked some other Maven packages and there the
policy is implemented correctly. The bug in libcommons-lang3-java could be
related to the relocation feature in the poms file but I haven't looked clo=
ser
yet.=20

Regards,

Markus

--=-WWu1/TyuruAhxvxDeZFM
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iQKTBAABCgB9FiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmFpZ1NfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQACgkQ2a0UuVE7
UeSYqw/+LM1ynvzi7yKky26ZJHdJcEZzXVu23r4vJGw+ROw28VXfyFBOEYHVFLFj
+FWeeojdXYZemfEV2OKol35yCkbGsQHf2JrfRMnVaSCEnDLR7RNTsFic96+rPUVm
VM0ixtMtBbhSLYkv98yf2ByjKKWRcQz0/aqUX+WKsAEyVQwxjfexurxNt4Ydsx9N
S6L2m92oGSfjjOPsgK6CWbSyz7DP5M+ZP2D4OHhj5J3WDqeyJcBwvLw6/MzwR7FM
c+AebDqZ5RsfrcXYKpfmy80GYUQYmacKfUIVH0FyLVz0B37OXCBW8eZX6bfs9v/0
3f69au51++/Hssy+qUc+pGh5B1V729e5OssAPILRIzGpJ4Ql2HEpZMOUY0/4Vl72
H9u8UxfdPvKN0dKmXq9VWQQlOz5jiDlKbIzxp89dGROaYGdr9BcXhG/DdoIEwfQI
AyNz/MDS6Wx9TjjtTVacZpU6tOhq/SktOXhcz/7UrGouGIUl1jvx6mThd1fp4+U+
RhFZSliAGDkprWgBOvQPzoNuCumx/FvA1WPvgpWH6AIa8qhKT5DY9W+uYAMtmXl9
rncBRahCJxbJDwXU9MtHDTYzXafFZJ6KfaTJUD00+ge5xmmqM+Tcwmz1CSa8s599
nOtf7jvpEMuDiy8ZJU+S8t12f/QnUrj92+G4NnhQiPyKBrepXkU=
=AY9Y
-----END PGP SIGNATURE-----

--=-WWu1/TyuruAhxvxDeZFM--