Github user khospodarysko closed the pull request at:
https://github.com/apache/maven-surefire/pull/121
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/120
@Tibor17 you have to follow the workflow described
[here](http://wiki.apache.org/commons/UsingGIT#Applying_Pull_Requests_.28for_git_based_components.29).
It's not possible to merge using the
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/120
>>Did you know, that it is possible to mark PRs as merged in GitHub?
I don't see such option in GUI. Is not it because of we are not the owner
of this repo `apache`?
Maybe they sould
Hello,
the branch with the first JUnit 5 IT is ready for reintegration. My
proposal is to create a separate branch for working on JUnit 5 so that we
can merge it to master only when all work on JUnit 5 support is done.
Regards,
Benedikt
Tibor Digana schrieb am Mo., 12.
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/118
@Tibor17 I've assed the assume statement using the API introduced in #120.
I propose that you create a new branch for JUnit 5, where we can merge this PR
and all follow up PRs for JUnit 5
Github user britter closed the pull request at:
https://github.com/apache/maven-surefire/pull/120
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/120
@Tibor17 thank you for integrating this. Did you know, that it is possible
to mark PRs as merged in GitHub? I've documented the workflow in the [Apache
Commons