On Thu, May 7, 2020 at 10:16 AM Ben Cotton bcotton@redhat.com wrote:
I adopted the maven-verifier-plugin package a while ago because it's a dependency of a dependency of a package I care about and I didn't want it to get retired. Now it is time to pay the piper. With the Java 11 change[1], maven-verifier-plugin fails to build. I know even less about Java than I do about most other things, so I'm hoping someone else can help (or feel free to take on this package if you want).
I tried bumping to the latest upstream and building in COPR[2] but it fails in a way that I don't understand. Any help would be greatly appreciated!
[1] https://fedoraproject.org/wiki/Changes/Java11 [2] https://download.copr.fedorainfracloud.org/results/bcotton/maven-verifier-pl...
I am having exactly the same problem with antlr3 and stringtemplate4. A web search shows that adding <source>8</source> to the maven-javadoc-plugin configuration is supposed to fix the problem, but for antlr3 and stringtemplate4 that just changes the failure to one of the form "Exit code: 1 - javadoc: error - The code being documented uses packages in the unnamed module, but the packages defined in https://docs.oracle.com/en/java/javase/11/docs/api/ are in named modules." Help!