You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Clément Guillaume (JIRA)" <ji...@apache.org> on 2018/12/24 19:34:00 UTC
[jira] [Commented] (SUREFIRE-1611) Deprecate skipTests in Failsafe
Plugin
[ https://issues.apache.org/jira/browse/SUREFIRE-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728509#comment-16728509 ]
Clément Guillaume commented on SUREFIRE-1611:
---------------------------------------------
Out of curiosity, will there still be a single parameter that allows disabling both failsafe and surefire tests at once?
> Deprecate skipTests in Failsafe Plugin
> --------------------------------------
>
> Key: SUREFIRE-1611
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1611
> Project: Maven Surefire
> Issue Type: Task
> Components: Maven Failsafe Plugin
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 3.0.0-M3
>
>
> We had an ambition to add prefixes surefire and failsafe in the old system properties which do not have them. At the same time we should remove {{skipTests}} from {{maven-failsafe-plugin}} because this have been associated with unit tests for long and thus {{maven-surefire-plugin}}. On the other side the {{maven-failsafe-plugin}} has a better property to use {{skipITs}}. Since the {{skip***}} system properties are so famous and have been used everywhere, we should not add prefixes for those; otherwise we broke all the world. We can make it with other system properties. We want to remove deprecated config parameters in the last milestone of {{3.0.0}}. One more reason to do these unpopular changes is the fact that system properties without prefixes interfere with other plugins.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)