Uncommon parent pom dependency configuration in Jackson 2.20/3.0

[seadbrane]

The parent pom (jackson-dataformats-binary) declares a compile dependencies on the main jackson-core packages, which have been omitted from the module pom dependency section. This is perhaps technically not a bug, but looks to be very rare as I have not yet been able to find another package that is setup this way.

https://mvnrepository.com/artifact/tools.jackson.dataformat/jackson-dataformats-binary/3.0.1
https://mvnrepository.com/artifact/tools.jackson.dataformat/jackson-dataformat-cbor/3.0.1

I do see that 2.20 dataformats-binary had a compile dependency.

https://mvnrepository.com/artifact/com.fasterxml.jackson.dataformat/jackson-dataformat-cbor/2.20.0

But the equivalent dependencies were also on the modules.
https://mvnrepository.com/artifact/com.fasterxml.jackson.dataformat/jackson-dataformat-cbor/2.20.0

I would recommend moving the compile dependencies down the modules as generally you are able to determine the runtime dependency requirements by just looking at the package without having to traverse up to the parent pom package.

[cowtowncoder]

@seadbrane Sounds like reasonable change request. I think it was solely done to reduce boiler plate, but if it is detrimental to tool usage we can definitely change that.

If you wanted, PRs against 2.x (2.21.0) and 3.x (3.1.0) would be much appreciated.