[MGNLTEST-191] Adjust enable clover profile execution phase Created: 24/Nov/21  Updated: 16/Nov/23

Status: Open
Project: Magnolia Test Framework
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Rishab Dhar Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: TAE
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split from MGNLTEST-186 Remove copy-pasted code from testcont... Closed
Template:
Acceptance criteria:
[ ]* enable-clover profile configuration is in parent pom
Task DoR:
Empty
Date of First Response:
Epic Link: TAE-build-or-infra-tasks
Team: Foundation

 Description   

Background

The enable-clover profile triggers at the verify stage which results in compilation failure if any code generation step in performed in magnolia code, because of duplicate classes being discovered by clover plugin.

The detailed explanation of the error can be found at https://openclover.org/doc/manual/4.2.0/kb--duplicate-class-errors-jaxb-or-jaxb2-plugin.html

As the test framework uses the grpc code generator plugin a similar issue to the jaxb2 code generator is found.

Currently, the test framework as a workaround overrides the enable-clover profile in the parent pom, by ensuring that the clover plugin gets triggered before the code generator plugin, that is clover plugin gets triggered at process-sources phase whereas the code generator at generate-resources phase.

This change in profile configuration should be pushed into the super parent pom of magnolia.



 Comments   
Comment by Christoph Meier [ 09/Nov/23 ]

rdhar  - since we're not using clover anymore bit jacoco instead - is this ticket still relevant?
If not - please close it. Thanks

Generated at Mon Feb 12 07:46:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.