[
https://jira.codehaus.org/browse/SUREFIRE-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358893#comment-358893
]
Andreas Gudian commented on SUREFIRE-1122:
------------------------------------------
Contributions in form of bug-fixes are always welcome :) - As for a
documentation, we have the pages on maven.apache.org, such as
http://maven.apache.org/guides/development/guide-m2-development.html - just
that for most parts of maven, including the surefire plugin, patches are best
submitted via GitHub pull-requests.
Other than that, we don't have any guide on how to get started with Surefire
development - most parts of the code are not that hard to understand. But I
must admit: this one here is tricky.
> When running failsafe with -Dfailsafe.rerunFailingTestsCount and parallel
> all, the reports are not generated correctly
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1122
> URL: https://jira.codehaus.org/browse/SUREFIRE-1122
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 2.18
> Reporter: Roy Arnon
> Assignee: Andreas Gudian
> Attachments: invalid.xml, test.zip, valid.xml
>
>
> Hi,
> I just tried the new feature -Dfailsafe.rerunFailingTestsCount on our
> failsafe build.
> Unfortunately, when running the build using parallel=all, it seems the junit
> xml files are not generated correctly.
> I've tried running it multiple different ways, including classedAndMethods,
> and all, but it seems to generate an incorrect xml file either way.
> I've attached both files here.
> I can provide a pom and java test case if required.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
