[
https://issues.apache.org/jira/browse/SUREFIRE-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961773#comment-15961773
]
Tibor Digana commented on SUREFIRE-1334:
----------------------------------------
[~apache-bugzi...@sebastian-kirsch.org]
[~sebastiankirsch]
Pls provide a fi in pull request.
You can add sanity checks in {{AbstractSurefireMojo}} and see already existing
sanity checks.
> Issue a warning in case argLine is set in conjunction with forkCount=0
> ----------------------------------------------------------------------
>
> Key: SUREFIRE-1334
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1334
> Project: Maven Surefire
> Issue Type: Wish
> Components: Maven Surefire Plugin
> Affects Versions: 2.18.1
> Reporter: Sebastian Kirsch
>
> I just spend some considerable amount of time figuring out why JaCoCo
> wouldn't work for a Maven project. The reason is that the JaCoCo Maven plugin
> sets the {{argLine}} property with a {{javaagent}} which causes the coverage
> to be generated and reported - but with {{forkCount}} being set to {{0}}, the
> {{argLine}} parameter has no effect.
> Now hindsight is 20/20, but I think it would be helpful if surefire would
> simply report a warning in case the {{argLine}} property is set, but will not
> have an effect.
> I assume the same is true for the {{systemProperties}},
> {{systemPropertiesFile}}, {{systemPropertyVariables}}, and maybe others.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
