+1
Regards,
Hervé
Le dimanche 3 juin 2018, 19:46:21 CEST Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121
> rsion=12343264
>
> There are still a couple of issues left in JIRA:
>
+1
Regards,
Hervé
Le dimanche 3 juin 2018, 16:35:31 CEST Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 7 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317522
> rsion=12343004
>
> There are still a couple of issues left in JIRA:
>
+1
On Tue, 5 Jun 2018 at 07:43, Michael Osipov wrote:
> Hi,
>
> We solved 25 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12341302
>
> There are still a couple of issues left in JIRA:
>
>
Important to know with any solution: JUnit3 doesn't understand skipped.
There are several approaches:
- start every test with a condition: if ( !supportsCvs() ) { return; }
this makes the tests run when possible and won't fail when not
available. However, tests will be marked as successfully
Am 2018-06-04 um 23:43 schrieb Michael Osipov:
Hi,
We solved 25 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12341302
There are still a couple of issues left in JIRA:
Hi.
In Maven itself and its plugins there's a deep hierarchy of test classes based
on `PlexusTestCase`, which extends `junit.framework.TestCase`.
Although we've been using the `Junit4` library for a long time, the actual
tests are still public unannotated methods, starting with the word
