Hi, Many of Maven plugins are targeted to build to JDK 8, but plugins are used to build projects which can use newer JDK.
So plugins must be targeted to minimum JDK use by projects which use plugins. Like in maven-plugin-tools, where we have an issue: https://github.com/apache/maven-plugin-tools/issues/944 When QDox will only support JDK 17+ it will not be possible to fix such issue On Fri, 22 Aug 2025 at 17:27, Paul Hammant <p...@hammant.org.invalid> wrote: > > I worked through a bunch of outstanding QDox issues. Well under direction, > Claude and JulesAgent did. I reached a snafu with something, and bumping > min-Java to 11 from 8 did the trick. I didn't think anything of it at the > time. > > One of the bug commenters reminded me that some maven-plugins use QDox. So > I should ask about java versions here. > > From https://mvnrepository.com/artifact/com.thoughtworks.qdox/qdox/usages, > I can see that these do: > > maven-javadoc-plugin > maven-compiler-plugin > maven-plugin-tools-annotations > plexus things > maven-plugin-tools-java > gmaven-runtime-support > maven-scr-plugin > (and others that I can't immediately guess are maven-core related) > > > Those maven bits and pieces can stick with the old version if they need JDK > 8, or course, and only people who need one of the new features for newer > java source grammars, could force an <excludes> upgrade for themselves. > > There's also the end of OSSRH portal for publishing which I've done in the > pom, but not yet all the form-filling online. Otherwise, I think I should > do a release soon, but y'all might have comments. > > - Paul -- Sławomir Jaranowski --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
