[MAGNOLIA-2413] Double check that magnolia-core-test is *not* deployed with clover's instrumentation code Created: 07/Oct/08  Updated: 17/Mar/09  Resolved: 20/Jan/09

Status: Closed
Project: Magnolia
Component/s: build
Affects Version/s: None
Fix Version/s: 4.0, 3.6.4, 3.6.5

Type: Task Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

I just had a weird issue where building (mvn install) a module (fckeditor or templating) would fail because one of the core-test classes was trying to initialize some clover stuff, while clover was not on the classpath. Rebuilding core (snapshot) fixed this.

We should ensure the final deployed artifacts of core do NOT contain the clover stuff.



 Comments   
Comment by Magnolia International [ 07/Oct/08 ]

3.6.3 seems fine, still wanna check for 3.7 again.

Generated at Mon Feb 12 03:36:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.