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 Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/146
@britter
@mgreau
Done.
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=70c8843e935882b0a78916894cb9f042964f2717
---
If your project is set up for it, you
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/146
---
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
Hi Plamen,
> Using GitHub as Maven repository?
Yup. At least to have it as a choice.
I'm imagining putting releases for my esoteric, long-tail ideas, on
Github *rather
than littering Maven Central.* But also allowing Maven/Grade/Ivy projects
to source the deps from there directly. The
Hi,
I think I had a similar idea. Could you please elaborate what you want to
achieve? Using GitHub as Maven repository?
I was looking at the matter myself. I didn't spend much time so I have only
basic understanding of the problems involved and how to solve them.
As far I know there are (even
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 britter commented on the issue:
https://github.com/apache/maven-surefire/pull/146
@Tibor17 I'm currently working on a `JUnitPlattformProviderInfo`. I have
some issues with the ITs, which I will bring up on the ML.
In the mean time, I need you to merge this PR. The
Hi,
We have some false positives in our Maven tests because Jenkins can't delete
old apache-maven-dist/lib/jansi-native on some nodes [1] (H24 in this case)
Do any of our Jenkins masters here know how to force the delete on every
nodes, so this issue from the past does not hit us?
Another idea
