|
Reverting to maven-compiler-plugin 3.2 (pre BUILD-206) doesn't fix the issue. Reverting to 3.1 does, but we've been on 3.2 since BUILD-165, i.e since poms 30)
|
|
That said, I don't see anything vital in the changelogs of 3.2 and 3.3, so reverting to 3.1 could be an option if we don't hear anything from Atlassian in the next few days.
|
|
Tentatively reverting to compiler 3.1. This generates a lot of warnings for unknown classes in javadoc (the generated stuff), but could be an OK workaround until Clover is fixed (for which I have a dubious local patch)
|
|
Decided to get back to compiler 3.3.
I sent a patch for the Clover plugin that seems to solve the problem, but I'm suspicious it won't be accepted as-is. Postponing until poms 32. Meanwhile, projects who generated code via APT can now easily disable clover thanks to BUILD-124.
|
Generated at Sun Feb 11 23:39:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.