Tibor Digana comments

Results 185 comments of


                                            Tibor Digana

[SUREFIRE-1494] default provider for JUnit4 integration tests is changed (from 'surefire-junit4' to 'surefire-junit47')

@dejan2609 If you have finished your work, we can start making the review here in GH.

[SUREFIRE-1494] default provider for JUnit4 integration tests is changed (from 'surefire-junit4' to 'surefire-junit47')

@dejan2609 Sorry, we were overloaded with preparation for Maven release, build fix, Resolver and Archetype.

[SUREFIRE-1494] default provider for JUnit4 integration tests is changed (from 'surefire-junit4' to 'surefire-junit47')

@dejan2609 The build is running https://builds.apache.org/job/maven-box/job/maven-surefire/job/SUREFIRE-1494/

[SUREFIRE-1494] default provider for JUnit4 integration tests is changed (from 'surefire-junit4' to 'surefire-junit47')

The build fails on `Caused by: java.lang.ClassNotFoundException: org.junit.runner.Computer` It means that we still have few tests which use JUnit 4 library. This is full log https://builds.apache.org/job/maven-box/job/maven-surefire/job/SUREFIRE-1494/1/consoleFull

[SUREFIRE-1494] default provider for JUnit4 integration tests is changed (from 'surefire-junit4' to 'surefire-junit47')

@dejan2609 Feel free to ping us whenever you have a spare time.

[SUREFIRE-1494] default provider for JUnit4 integration tests is changed (from 'surefire-junit4' to 'surefire-junit47')

@dejan2609 I had to concentrate mostly on my private life and concentrate only on ASF issues which must be solved at right time. This issue we are talking about in...

[SUREFIRE-1494] default provider for JUnit4 integration tests is changed (from 'surefire-junit4' to 'surefire-junit47')

I think it is still very valuable.

[SUREFIRE-1494] default provider for JUnit4 integration tests is changed (from 'surefire-junit4' to 'surefire-junit47')

Hi @dejan2609 can you pls rebase this PR? thx

[SUREFIRE-1494] default provider for JUnit4 integration tests is changed (from 'surefire-junit4' to 'surefire-junit47')

@dejan2609 You are welcome.

[SUREFIRE-2095] Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true when run with failsafe

@br0nstein Thx for the fix in the verifier mojo. I admit the commit [6e60b03](https://github.com/apache/maven-surefire/commit/6e60b0389814d8361e453092d3b18f52c3e4bcb1) was not done so well. The situation with XML reports is even more complicated if you...