[jira] [Resolved] (SLING-4835) jacoco-it report missing if maven-failsafe-plugin:argLine is used

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz resolved SLING-4835.
----------------------------------------
    Resolution: Fixed

As per the trick is to set argLine in the pom properties, so that the jacoco plugin appends to it.

I have fixed this in the contentdetection and contentloader modules, building with -P jacoco-report now correctly produces 3 reports as per SLING-4760

The downside is that options added to that argLine is now used by both the surefire and failsafe plugins - if surefire needs a different argLine it will need to be declared in that plugin's config.

> jacoco-it report missing if maven-failsafe-plugin:argLine is used 
> ------------------------------------------------------------------
>
>                 Key: SLING-4835
>                 URL: https://issues.apache.org/jira/browse/SLING-4835
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>
> In {{bundles/commons/contentdetection}} for example, using our parent pom 23, the {{target/site/jacoco-it}} report is not generated.
> That's probably because the pom uses the maven-failsafe-plugin {{argLine}} setting to set the jvm memory. The jacoco plugin also sets that to activate its agent, but I suppose that's ignored as {{argLine}} is already set by the pom, so the agent is not activated for the integration tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)