[infinispan-issues] [JBoss JIRA] (ISPN-10043) Add explicit dependency on surefire-testng

[Tristan Tarrant (Jira)]

     [ https://issues.jboss.org/browse/ISPN-10043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tristan Tarrant updated ISPN-10043:
-----------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> Add explicit dependency on surefire-testng
> ------------------------------------------
>
>                 Key: ISPN-10043
>                 URL: https://issues.jboss.org/browse/ISPN-10043
>             Project: Infinispan
>          Issue Type: Task
>          Components: Build
>    Affects Versions: 10.0.0.Beta2, 9.4.9.Final
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>            Priority: Major
>             Fix For: 10.0.0.Beta3, 9.4.10.Final
>
>
> We need to be able to collect all the dependencies in a private repository and run the build without access to Maven Central for the product.
> {{maven-surefire-plugin}} doesn't have an explicit dependency on {{surefire-testng}}, instead it resolves it dynamically when it finds {{TestNG}} in the classpath. This means {{surefire-testng}} and its transitive dependencies are not detected automatically and need to be imported manually. 
> When a dependency is not imported, it is pretty hard to debug: there is only a warning during the build:
> {noformat}
> [WARNING] Missing POM for org.apache.maven.surefire:surefire-testng-utils:jar:3.0.0-M3
> {noformat}
> And then the failure message only mentions a specific class:
> {noformat}
> There was an error in the forked process
> org/apache/maven/surefire/testng/utils/Stoppable
> {noformat}
> We should add an explicit dependency on {{surefire-testng}} on core, like the modules using {{JUnit}} have an explicit dependency on {{surefire-junit47}}, in order to allow automatic detection of its transitive dependencies and to get better error messages.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)