[
https://issues.apache.org/jira/browse/OAK-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861033#comment-15861033
]
angela commented on OAK-5623:
-----------------------------
ok... but that also mean that it's prone to cause false positive failures
noise, which obviously wasn't the intention... I set the value based on the
failing report on my machine (starting with an unrealistic value).
initial investigation: i initially run the build with java 1.7 (-> 0.75). when
running with java 1.8 i get the same failure as you get :-). if that pattern
was consistent we can use the most conservative number.
> Enforce minimum line coverage for security related modules
> ----------------------------------------------------------
>
> Key: OAK-5623
> URL: https://issues.apache.org/jira/browse/OAK-5623
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: auth-external, auth-ldap, authorization-cug, parent
> Reporter: angela
> Assignee: angela
> Fix For: 1.7.0
>
> Attachments: OAK-5623.patch
>
>
> I would like to use jacoco-maven-plugin to run an additional verification
> upon module build to make sure the line coverage with test cases is
> maintained while evolving the source.
> The attached patch extends the existing plugin definition for
> jacoco-maven-plugin in the parent pom.xml and enables the verification with
> the following modules:
> - auth-external
> - auth-ldap
> - authorization-cug
> Since the patch modifies the parent pom.xml I would like others to review
> this as well. Will send out notification to the list.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
