> > >The question I am asking myself is : Are Cactus users willing to accept
>this
> > >package name change ? Will it cause big troubles ? Should we do it as the
> > >same time as we release version 1.2 or should we wait longer ?
> > Yes... although I can foresee all sorts of fun working out which package
> > I'm actually using...
> >
>
>why ? There would be only one package : org.apache.cactus
Sorry - I should have said jar... It's always surprising how many copies
of xerces, cactus, ant, servlet.. etc. I have floating around on my machine ;)
> > There's no way to deprecate a package, is there? The only idea that comes
> > to mind would be to deprecate the provide two implementations of
> > ServletTestCase - one in the old package, with all the methods deprecated,
> > and the new one (which would be identical, except the deprecation). That
> > way at least we'd get fair warning about the change...
>
>Jim,
>That won't work out as it is not only ServletTestCase that is impacted but
>all Cactus classes used to write test cases (there are about 15). The only
>solution I know of is a new version.
Well, go for it then! It'll be a case of search 'n replace to fix, but
that's not really that much of a problem.
--
* Jim Cheesman *
Trabajo:
[EMAIL PROTECTED] - (34)(91) 724 9200 x 2360
Not only am I
redundant and superfluous, but I
also tend to use more
words than necessary.
