[ 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,
[ http://jira.codehaus.org/browse/MAVEN-1397?page=comments#action_45828 ]
Andy Glick commented on MAVEN-1397:
---
In Brett's comment of 9 August above, he stated the that among the
preconditions for going forward with the backport of the surefire plugin to M1
[ http://jira.codehaus.org/browse/MAVEN-1397?page=comments#action_45078 ]
Trygve Laugstol commented on MAVEN-1397:
I'm not sure what the best way is, there are at least two solutions to this:
1) The easy way Add setters to the Mojo and use it as a no
[ http://jira.codehaus.org/browse/MAVEN-1397?page=comments#action_45077 ]
Andy Glick commented on MAVEN-1397:
---
Brett , Trygve & Emmanuel,
I took Trygve's suggestion and I grabbed the surefire code from codehaus svn. i
grabbed the maven 2 code and built it
[ http://jira.codehaus.org/browse/MAVEN-1397?page=comments#action_44487 ]
Trygve Laugstol commented on MAVEN-1397:
You can get the Surefire sources here:
https://svn.codehaus.org/surefire/trunk/surefire/
> replace test plugin with surefire
> --
[ http://jira.codehaus.org/browse/MAVEN-1397?page=comments#action_44486 ]
Andy Glick commented on MAVEN-1397:
---
Brett,
I set out to figure out how to help with the surefire port rather than on the
m1 test plugin. Unfortunately, I seem to be missing the inf
[ http://jira.codehaus.org/browse/MAVEN-1397?page=comments#action_44218 ]
Brett Porter commented on MAVEN-1397:
-
no date on the 1.1-beta-2 as yet.
Basically, some things need to happen:
1) m2 surefire plugin gets up to feature level of m1 test plugin
2)
[ http://jira.codehaus.org/browse/MAVEN-1397?page=comments#action_44187 ]
Andy Glick commented on MAVEN-1397:
---
I recently posted to the Maven Users list, stating that I was going to work on
the Jelly maven-test-plugin and attempt to allow all of the user v
