Github user asfgit closed the pull request at:
https://github.com/apache/maven/pull/62
---
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 feature is
Github user mfriedenhagen commented on the pull request:
https://github.com/apache/maven/pull/62#issuecomment-127376555
Hello,.just out of curiosity: why did you use the old junit3 mechanism?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user atanasenko commented on the pull request:
https://github.com/apache/maven/pull/62#issuecomment-127380233
Hi, I took a look at a couple of neighboring tests and was convinced all of
them are junit3
---
If your project is set up for it, you can reply to this email and have
Github user atanasenko commented on the pull request:
https://github.com/apache/maven/pull/62#issuecomment-127386965
I've updated to junit4, looks more modern now :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
GitHub user atanasenko opened a pull request:
https://github.com/apache/maven/pull/62
MNG-5805: Fix NPE in LifecyclePhase#toString()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/atanasenko/maven master
Alternatively you can
