Re: [Mockobjects-java-dev] UnsupportedOperationException

[<ma...@bt...>]

>MockNotImplementedException (for the not implemented methods) and
> MockNotSupportedException (for the not supported methods).

I am happy with this suggestion.

> I don't agree here ... (once more :) ). There has been 3 versions of java
> since 1.1 (1.2, 1.3 and now 1.4). It is normal to drop support for 1.1.
> *all* the I have seen have already dropped support for 1.1 or are seriously
> considering it ... Even JUnit is considering dropping it in its next
> version.

The biggest code base of MockObjects is the Connextra code base, they are stuck in 1.1.8 at the moment - there is no compelling reason not to support 1.1.x as we aren't doing anything fancy. The only unique feature is auto-validation of verifiables, and in the core project it is no bit problem to keep the manual verify methods.

I don't mind having to import a compatibility set of classes - and with careful use of non specific import lines (especially in java.util.*) we can do this.

I think it is totally unfair to shaft Connextra on this especially as most of the work on Mock objects came from that team and they kindly donated the foundation of the current code base. As it is easy to support 1.1.x I think we should.

Tim