[BUILD-23] Don't install nor deploy clover-instrumented artifacts Created: 28/Oct/09  Updated: 13/Apr/17  Resolved: 28/Oct/09

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

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

Issue Links:
relation
is related to BUILD-196 maven-clover2-plugin installs and ove... Closed
Template:
Acceptance criteria:
Empty

 Description   

This is causing issues such as MGNLEE-162 - clover-instrumented get installed in our local repositories, and somehow, despite them being built with the correct name (...-bundle-clover.zip for instance), they end up being copied to the local repo as ..-bundle.zip, thus overriding the "real" bundle. This does not affect the deploy phase, which is why this is only occuring when the same local repo was used to build module-bundles and the ee-bundle, for instance.

We can avoid this by using the instrument-test goal instead of instrument.
See http://forums.atlassian.com/thread.jspa?messageID=257322053


Generated at Sun Feb 11 23:38:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.