RE: James / Excalibur ThreadPool conflict

Peter,

> > I'm very confused.  This interface is actually marked deprecated.  =
So
> why
> > would the deprecated interface be changed?
> >
> > Moreover, why is the replacement interface
> > (org.apache.excalibur.thread.ThreadPool) not changed?  It still has =
the
> > execute(Runnable) method.  In fact, it has both methods.
> >
> > Can anyone shed any light on this?
>=20
> If you update to latest version of everything then everything should =
still
> work. The problem is that an old jar is being used by one thing and an =
old
> one by another. If everything is compiled against old jar then you are
> fine.
> If anything is compiled against new jar then you need the new jar ...
>=20
> I can't spot anybackward incompatible interface changes. Can anyone
> indicate
> where this is?

A method was removed from the =
org.apache.avalon.excalibur.thread.ThreadPool
interface.  Specifically, the execute(Runnable) method.  As I said =
above,
considering the interface was already deprecated I don't understand why =
this
method was removed.  Seems to violate the whole point of deprecating
interfaces.

Everything does work if you compile/run/etc. against the old jar.  No =
one is
debating that point (see Stephen's earlier email).  The confusion is =
about
the reason behind the change.

--Peter