You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Andy Glick (JIRA)" <ji...@codehaus.org> on 2005/09/05 17:40:03 UTC
[jira] Commented: (MAVEN-1397) replace test plugin with surefire
[ 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 was that the "...m2 surefire plugin gets up to feature level of m1 test plugin ".
A naive survey of the situation might lead someone to believe that such an event might be a long way off, for 3 reasons:
1) the surefire plugin does not generate an XML for JUnit tests
2) a JUnit report contains in addition to the test case results, a whole list of properities and values from the underlying Ant environment, since M1 is executing the Ant JUnit task
3) the current surefire plugin works, andf there are plenty of things that don't work :-), so why invest core team energy where it isn't required to meet upcoming deliveries?
As an outsider with no coding assignments, and having volunteered to work on this, I've been looking at the surefire report package and at the Ant JUnit optional task package, and some sort of XML report of the test results shouldn't be too hard to come up with, but I have understood from the users list that there is no agreement on a candidate "properties set" that would be added to the XML report to provide a feature level match.
I'm sure that I've left out other features towards the feature level. If someone would be willing to enumerate them, I'd be willing to take a crack at adding them.
In Trygve's comment above of 23 August, he spoke about creating an infrastructure for embedding M2 into an M1 environment. Has anyone made any progress on that, and if so, where would I look to find the code?
One more question if you will, is there any reason why I shouldn't go ahead and rework the m1 test plugin and the m1 itest plugin by modifying the existing jelly code and either 1) refactoring some behavior or 2) simply exposing all of the necessary configurable parameters of the test plugin?
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org