[
https://issues.apache.org/jira/browse/SUREFIRE-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033730#comment-16033730
]
Tibor Digana commented on SUREFIRE-1378:
----------------------------------------
System properties are simple but we have another config parameters which are
complicated and users have different needs. So I would like to give you chance
with all parameter with same principle of extensions in version 3.0 and not
partially with this parameter in current version.
> Nice to have systemPropertiesFile configurable by user property
> ---------------------------------------------------------------
>
> Key: SUREFIRE-1378
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1378
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Reporter: Michal Domagala
> Priority: Minor
>
> I would like to have option to configure my tests with property files. But
> property file is not required, because in 95% my tests work fine with default
> configuration.
> I used the following workaround: I configured failsafe plugin in the
> following way
> {code:xml}
> <properties>
> <my.test.props.file></my.test.props.file>
> </properties>
> (...)
> <artifact>maven-failsafe-plugin</artifact>
> (...)
> <systemPropertiesFile>${my.test.props.file}</systemPropertiesFile>
> {code}
> In 95% I call *mvn verify*, systemPropertiesFile is not found and ignored
> -all pass
> In 5% I call *mvn verify -Dmy.test.props.file=x.props*
> The problem is in 95% I get warning about missing files. Also configuration
> is unnecessary complicated
> I would like drop whole connfiguration from pom.xml and use:
> In 95% *mvn verify*
> In 5% *mvn verify -Dfailsafe.systemPropertiesFile=x.props*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
