Superfluous build notifications in JIRA

Hi all, Last Thursday and Friday, I've received well over 400 notifications from Apache JIRA, all by the "Hudson" user (now Jenkins). They notified me of a failed job regarding a ticket I was watching. Not only does it annoy me, it also annoys people who reported a ticket [1]. As far as I

[GitHub] [maven-archiver] mabrarov commented on pull request #10: [MSHARED-955] make parseOutputTimestamp static

mabrarov commented on pull request #10: URL: https://github.com/apache/maven-archiver/pull/10#issuecomment-763180478 Is this PR still actual? This is an automated message from the Apache Git Service. To respond to the

Re: Follow-up PR for JUnit 5

+1000 was expected since years (using rule with junit4 before junit5 comes out) and ease contributions a lot Thanks a lot Guillaume for all that work Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Follow-up PR for JUnit 5

I've pushed a PR following up the switch to JUnit 5 which includes two commits: - the use of standard parameterized tests (for speed, I initially reused the stuff I wrote for Camel which leads to a smoother migration from junit 3/4 parameterized tests, but given there are only 2 test classes