Re: JUnit 4.12-beta-1 is released

Hi,

I've tried porting an in-house runner that previously has been using 4.8 into 4.12-beta-1 and and I've found no issues that must be fixed. So to me it looks ready for release.

One thing that was slightly annoying is that instead of removing org.junit.internal.AssumptionViolatedException, you've deprecated and duplicated it into org.junit.AssumptionViolatedException. This caused me some headache as we had code catching the former class type and suddenly it looked like assumptions had stopped working until I realized I had to change the import statement. For the future, I'd prefer that you just remove the original class as then we'll get a compiler error instead of runtime failures.

And just as one extra data point: I'm all in favor of you removing old deprecated classes as you've done with the runner that another poster disagreed with. I had no problems at all with that part of the porting of our runner.

By the way, do you have any estimates on when 4.12 will be released? I'm in progress of upgrading our junit-dependency and would like to do that to 4.12 directly and don't have to go to 4.11 and upgrade again in a month or two. So if you have an estimated release date, I can plan accordingly.

BR,
  Chris