[SUREFIRE-352] Get rid of hardcoded TestNG dependency name.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3
• Fix Version/s: 2.3.1, 2.4
• Component/s: TestNG support
• Flags: Patch
• Assignee: Mauro Talevi
• Reporter: jdoe
• Created: 28/Aug/07 13:41
• Updated: 05/Apr/15 14:53
• Resolved: 21/Nov/07 05:21

Description

The name of the TestNG dependency is hardcoded ('org.testng:testng'). Some ppl are using internal repositories where artifacts are published under different names. It would be nice to able to specify the name of dependency, e.g.:

build.pom

<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-surefire-plugin</artifactId>
	<version>2.4-SNAPSHOT</version>
	<configuration>
		<testNGDependency>testng:testng</testNGDependency> <!-- custom dependency name -->
		<suiteXmlFiles>
			<suiteXmlFile>testng.xml</suiteXmlFile>
		</suiteXmlFiles>
	</configuration>
</plugin>

Proposed patch attached.

Issue Links

• relates to: SUREFIRE-141 Surefire should provide a pluggable means to specify a custom provider