raboof commented on PR #714: URL: https://github.com/apache/commons-parent/pull/714#issuecomment-5036264251
This thread seems rather goalpost-moving... > It's not for us that this matters, but for downstream users like some Linux distros that require building from sources. We do have such users and it would be a surprise for them. Which Linux distro's is that? Even the notoriously-slow Debian Stable builds with JDK 21 (https://deb.debian.org/debian/pool/main/libc/libcommons-compress-java/libcommons-compress-java_1.27.1-2.dsc, https://packages.debian.org/trixie/default-jdk), 'oldstable' is jdk17 (even 'oldoldstable' is jdk11). Gentoo (https://packages.gentoo.org/packages/dev-java/commons-compress, https://packages.gentoo.org/packages/virtual/jdk) also seems to use newer JDK's. > We really don't gain anything by changing the build platform requirement and making it different from the runtime requirement. It's just confusing. Well, it holds us back from upgrading our build dependencies, leaving us on possibly-unsupported versions. In this case it might not be so bad (there's been pretty recent junit 5 releases), but it also disconnects us from upstream, making it effectively useless to provide feedback or contribute otherwise. The target audience that's impacted by a difference in build platform requirements vs runtime requirements seems unlikely to be too confused, I'm sure they'll manage. Anyway, I created https://github.com/apache/commons-parent/pull/718 to go back to junit 5 for now. That said I really think we should at least reconsider our dependabot approach here (I see this has been discussed before in #707). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
