Trouble with commonly used Maven plugins

[Sanne Grinovero]

Hello all,

Tomaz and myself work respectively on the WildFly and Hibernate teams; Rory O'Donnell kindly sends us reminders about each new JDK preview build so that we use these popular OSS projects and their extensive testsuites to verify early changes to the JDK, and possibly also to get a sense of the impact of changes on larger communities.

It turns out that the "plexus-archiver" [1] library fails because of the Verona change; the fix is trivial of course as they just need to adjust the couple of lines which implement a version check, and Tomaz will send it to the Plexus team soon.

Still, please consider that this library is very commonly used by build tools. In particular Maven uses it to implement the maven-jar-plugin, maven-source-plugin, and others. But while several of these are optional, the maven-jar-plugin is an essential component for most builds.

It's a common pattern among Maven users to run the compilation and packaging with the same JVM as the one running the testsuite, so the unfortunate news here is that it seems a large population will have difficulties in testing JDK9 until this trivial patch to plexus-archiver will make its way in a Plexus release, and then gets picked up by a Maven release.

I won't ask you to change or revert things as I agree this is a nice improvement, and thank you all for it!
Just bear in mind that migrations and more feedback will be a bit slower than usual.

Thanks,
Sanne

1 - https://github.com/codehaus-plexus/plexus-archiver