cannot have --archive option with --harness

[Michael Peters]

Eric Wilhelm wrote:
> I was just attempting to demonstrate to Colin how our new parrot 
> TAP::Harness subclass could be used with TAP::Harness::Archive... oops.
> 
> I think we really need that to be a mixin or something.

I'm not sure a mix-in will really work since TAP::Harness::Archive overrides
new() and runtests() which are probably the 2 most important methods.

How about changing your custom subclass to inherit from TAP::Harness::Archive
instead of TAP::Harness and then we change runtests to use T::H::A only when
--harness is not specified and assume the user knows that his --harness needs to
inherit from T::H::A when using --archive? Either that, or push archive support
into T::H (which I'm not sure should happen).

-- 
Michael Peters
Developer
Plus Three, LP