version 5.0.3, which I hope to upload as soon as possible, will
implicitly solve this bug, because is drops the distinction between the
two artifacts (and it adopts only Apache-2.0). I see no point in adding
compatibility POMs, because the groupId and artifactId are changing
anyway, so it is better to directly divert reverse dependencies to these.

Thanks, Giovanni.
Giovanni Mascellani <g.mascell...@gmail.com>
Postdoc researcher - Université Libre de Bruxelles


Attachment: signature.asc
Description: OpenPGP digital signature

This is the maintainer address of Debian's Java team
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to