Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/141
@Tibor17 I'm not working on the 3.0 branch any more. It's up to you. I
think the 3.0 branch should have version 3.0.
---
Github user KroArtem commented on the issue:
https://github.com/apache/maven-surefire/pull/141
Well, 3.0 also becomes highly appreciated as JUnit 5 was officially
released recently.
---
-
To unsubscribe, e-mail:
Github user KroArtem commented on the issue:
https://github.com/apache/maven-surefire/pull/141
Not sure about 3.0 stuff but 2.20.1 with last fixes is highly forthcoming.
ð
---
-
To unsubscribe, e-mail:
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/141
@britter
I think this was forgotten. Should I process it?
---
-
To unsubscribe, e-mail:
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/141
@britter
I think the version is not mandatory right now. I have to anyway replay
each commit and squash in one on the top of future origin master.
---
If your project is set up for it,
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/141
@Tibor17 so we can merge this to 3.0-rc1 branch? Than the branch will have
the correct SNAPSHOT version.
---
If your project is set up for it, you can reply to this email and have your
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/141
No worries about the commit if it is messy.
I will pick up every single commit, make a patch and apply to master.
On Mon, Jun 5, 2017 at 10:30 AM, Benedikt Ritter
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/141
@Tibor17 this and #146 a targeted at the 3.0-rc1 branch. So they won't
interfere with the release of 2.20.1.
Regarding junit5 support: it is currently pretty messy and I'm to blame
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/141
@britter
We have to finish 2.20.1 but we can finish the junit5 provider. Where did
we finish last time?
---
If your project is set up for it, you can reply to this email and have your
Github user michael-o commented on the issue:
https://github.com/apache/maven-surefire/pull/141
2.20.1 will go first.
---
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
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/141
@Tibor17 what about this?
---
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
11 matches
Mail list logo
