Hi,
Working on libjackson2-* upgrades on the side I'm experimenting
introducing a build-dependencies metapackage [1] to avoid repeating them
all in every package that build-depends on libjackson2-core-java.
It works so far, but I'm not completely sure it's an appropriate way to
deal with the issue. Among the advantages, any update of jackson-core
(that ships the parent POMs used by other jackson-* builds) changing the
set of build-dependencies will be automatically pulled by the other
packages without needing to update them individually, and that may help
prevent future build failures. Among the possible issues, these build
deps are now transitive, and some tooling may miss the need to rebuild
and retest the package after one of these b-d is updated but not
jackson-core itself.
WDYT?
Cheers,
[1]:
https://salsa.debian.org/jpd/jackson-core/-/blob/981930044f8e4097d866c6837cd8c8b8b45ecc54/debian/control#L62-L94
--
Julien Plissonneau Duquène
