Packaging mustangproject
Julien Plissonneau Duquène
sre4ever at free.fr
Sun Feb 2 19:03:15 GMT 2025
Hi Mechtilde,
Le 2025-02-02 17:28, Mechtilde Stehmann a écrit :
>
> I discovered that most of the dependencies are not defined in the
> pom.xml files.
>
> What is the proper way to handle it? To patch the *.xml files in a
> patch queue? Or is therer a better way?
It depends on what the dependency is needed for. You could take a look
at how commons-io [1] is packaged, as it is a rather simple, clean and
typical package. It uses dh --buildsystem=maven aka the
maven-debian-helper [2] which in turn uses the maven-repo-helper [3].
In the case of commons-io, all the extra unnecessary dependencies were
simply added to maven.ignoreRules. The maven-debian-helper has its own
way of patching the POMs independently of the usual patch queue.
For more complicated situations you may have to patch the POMs in other
ways (e.g. with the patch queue), patch the source code to remove
references to the missing libraries (which usually also means removing
features), or even package the missing dependencies.
Cheers from Brussels,
[1]:
https://sources.debian.org/src/commons-io/2.18.0-1/debian/maven.ignoreRules/
[2]: https://wiki.debian.org/Java/MavenDebianHelper
[3]: file:///usr/share/doc/maven-repo-helper/reference.html
--
Julien Plissonneau Duquène
More information about the pkg-java-maintainers
mailing list