Jon Stevens wrote:
>
> Case in point: The changes that Sam quoted with regards to
> Turbine breaking Jetspeed in a single tinderbox build were
> mitigated by the fact that the Jetspeed developers asked
> for those changes to happen in the first place. That is a
> tiny little bit of very important context that Sam
> conveniently left out. :-)
Single? I won't quibble. ;-)
Are you saying that this could not have been implemented in a way that
permitted a smooth migration? Or that the JetSpeed developers specifically
asked that there not be a transition period?
Both the impending Tomcat 3.3 and Tomcat 4.0 look considerably different
internally than the original Tomcat 3.0. But the overwhelming majority of
the servlets that ran on Tomcat 3.0 will run on either. The reason? The
much maligned JCP views the servlet API as a contract.
The desire to work together is core to my thesis that there is a Jakarta
community here.
> With regards to Cocoon, he also left out the fact that we
> DID in fact mark those changed database pool API's as
> deprecated for a few months before removing the deprecated
> code.
The reason I left that out is that I was unaware of it. My apologies.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
