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 2018/12/18 00:34:00 UTC

[jira] [Closed] (SUREFIRE-1611) Deprecate skipTests in Failsafe Plugin

     [ https://issues.apache.org/jira/browse/SUREFIRE-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tibor Digana closed SUREFIRE-1611.
----------------------------------
    Resolution: Done
      Assignee: Tibor Digana

https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=7ae14167887bf4faeac92141e39ae732f5b12ba6

> 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)