ma., 22.11.2010 kl. 16.05 -0500, skrev Jason van Zyl: > What if we provided some of a core utilities like the classpath scanning, > forking, and reporting services and made individual plugins like a > junit-maven-plugin, and testng-maven-plugin? This is what I am working on ATM. Getting the utilities extracted and loosely coupled. If we build some simple provider detection mechanism into surefire we could probably just leave the question of the plugin parameters for later, assuming that most modern testing architectures will require less configuration and not more.
I feel I'm not entirely comfy with how to express the "dispatcher" role that the current surefire plugin has, where it passes on control to specific providers - currently this is expressed in the mother of all big ugly if-blocks within the existing plugin. And it seems to me like this must be handled in some way ? (Or we could just request people to disable surefire in their pom when they upgrade to testng-maven-plugin, or maybe the testng-maven-plugin could just disable surefire by its mere presence) > I know that Cedric would work on a testng-maven-plugin but isn't overly keen > on working on Surefire. I hope he'll take another look in a week or two when I finish 2.7; which is my current goal - give or take a week. Kristian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
