[infinispan-issues] [JBoss JIRA] (ISPN-11254) Remove maven-failsafe-plugin in infinispan-server-runtime

[Ruslan Khasbulatov (Jira)]

    [ https://issues.redhat.com/browse/ISPN-11254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990458#comment-13990458 ] 

Ruslan Khasbulatov commented on ISPN-11254:
-------------------------------------------

Hi Dan, as far as I understood the problem, we need to handle *skipTests* flags for both plugins:

https://maven.apache.org/surefire/maven-surefire-plugin/examples/skipping-tests.html
https://maven.apache.org/surefire/maven-failsafe-plugin/examples/skipping-tests.html

The most appropriate place to change is *pom.xml* in *infinispan-integrationtests-parent*


> Remove maven-failsafe-plugin in infinispan-server-runtime
> ---------------------------------------------------------
>
>                 Key: ISPN-11254
>                 URL: https://issues.redhat.com/browse/ISPN-11254
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Server, Test Suite
>    Affects Versions: 10.1.1.Final
>            Reporter: Dan Berindei
>            Priority: Minor
>             Fix For: 11.0.0.Final
>
>
> {{infinispan-server-runtime}} uses both {{maven-surefire-plugin}} and {{maven-failsafe-plugin}}, which makes it confusing sometimes. E.g. when trying to run a single integration test with {{-Dit.test=SomeIT}}, the surefire tests still run.
> {{maven-failsafe-plugin}} 3.0.0 is supposed to replace {{-DskipTests}} with {{-DskipITs}}, so both {{-DskipTests -Dit.test=SomeIT}} and {{-DskipITs -Dtest=SomeTest}} will work. They haven't yet removed it in version 3.0.0-M4, but if we decide to keep both plugins after all, we can emulate the new behaviour with
> {code:xml}
>                <skipTests>${skipITs}</skipTests>
> {code}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)