You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2015/06/05 22:57:01 UTC
[jira] [Closed] (MSHARED-418) Verifier should not use hard coded
CLI options without possibility to modify them
[ https://issues.apache.org/jira/browse/MSHARED-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tibor Digana closed MSHARED-418.
--------------------------------
Resolution: Fixed
commited in SVN #1683964
https://svn.apache.org/repos/asf/maven/shared/trunk/maven-verifier
> Verifier should not use hard coded CLI options without possibility to modify them
> ---------------------------------------------------------------------------------
>
> Key: MSHARED-418
> URL: https://issues.apache.org/jira/browse/MSHARED-418
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-verifier
> Affects Versions: maven-verifier-1.5
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Fix For: maven-verifier-1.6
>
>
> Verifier used -e and -B by default. These CLI options violate my ITs in surefire and I need to fully control the CLI options in integration tests. Introduced new constructor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)