[ http://jira.codehaus.org/browse/MAVEN-1397?page=comments#action_45831 ]
Trygve Laugstol commented on MAVEN-1397: ---------------------------------------- 1) As you're saying this shouldn't be hard. Just add a new surefire reporter 2) I don't think that this is a really important feature, the Maven 1 plugin doesn't use it for anything in particular. And I'm pretty sure it's just a dump of System.getProperties() 3) Well, you asked for something to do :) One major feature I know that's missing is the ability to fork the tests, which I see as the biggest issue to fix. I haven't looked into making some infrastructure for embedding Maven 2 in Maven 1 yet but I don't think it's strictly needed for this plugin. I think that doing this plugin "by hand" might give a more clear overview over what's really needed. > replace test plugin with surefire > --------------------------------- > > Key: MAVEN-1397 > URL: http://jira.codehaus.org/browse/MAVEN-1397 > Project: Maven > Type: Task > Reporter: Brett Porter > Assignee: Emmanuel Venisse > Priority: Blocker > Fix For: 1.1-rc1 > > > avoid the need for forkmode=once by switching to the superior surefire plugin > for general testing. > Enhance the surefire mojo to provide the same output as junit so that the > test plugin remains backwards compatible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
