[BUILD-211] When running Clover, compiler still generates code twice, leading to duplicate classes Created: 04/May/15  Updated: 06/May/22  Resolved: 06/May/22

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to BUILD-207 Classes generated with APT are consid... Closed
is related to BUILD-165 Specify all versions of Maven plugins... Closed
is related to BUILD-206 Update Maven compiler plugin to 3.3 Closed
Template:
Acceptance criteria:
Empty

 Comments   
Comment by Magnolia International [ 05/May/15 ]

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)

Comment by Magnolia International [ 05/May/15 ]

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.

Comment by Magnolia International [ 05/May/15 ]

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)

Comment by Magnolia International [ 07/May/15 ]

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.