You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/01/11 09:22:00 UTC

[jira] [Commented] (SLING-10054) Get rid of emma-maven-plugin and related profile

    [ https://issues.apache.org/jira/browse/SLING-10054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262510#comment-17262510 ] 

Konrad Windszus commented on SLING-10054:
-----------------------------------------

[~radu] Since you worked a bit on code coverage, do you know if those two profiles are still in use by someone?

> Get rid of emma-maven-plugin and related profile
> ------------------------------------------------
>
>                 Key: SLING-10054
>                 URL: https://issues.apache.org/jira/browse/SLING-10054
>             Project: Sling
>          Issue Type: Improvement
>          Components: General
>            Reporter: Konrad Windszus
>            Priority: Major
>             Fix For: Parent 41
>
>
> Our parent pom.xml contains a profile with id {{emma}} leveraging the {{emma-maven-plugin}} from org.codehaus (https://github.com/apache/sling-parent/blob/de3d9c8255fa84a62a7be921127376a817309bd9/sling-parent/pom.xml#L402). As we now do the coverage reporting with profile {{jacoco-report}} and the {{jacoco-maven-plugin}} we should get rid of the {{emma}} profile and most probably also of {{emma-report}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)