cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <>
Subject [Heads Up] Deprecation Resolution and Future Concerns
Date Wed, 05 Feb 2003 19:03:31 GMT
The Avalon team voted in favor of using a softer form of deprecation for
the org.apache.avalon.framework.component package.  The Recomposable
class remains deprecated, but this should not affect any Cocoon users.
No known container supports it, and it is a bad design that was carried
forward from the Avalon 3.x days.

What this means is that in addition to providing binary compatibility
with all your users, the deprecation messages from Javac will reflect
Cocoon deprecations.

We will be releasing the Avalon projects a step at a time.  Each step
will be compatible with the currently released versions of all the
software.  We will have a new released ECM in the very near future

The new ECM will have some changes, some for the better and some that
might cause some changes for you.  One change for the better is that
we backported the *-complete-*.jar feature from Fortress.  That means
all Excalibur JARS necessary for ECM to run will be in one large JAR
file.  The CVS version does not use Excalibur Collections or Excalibur
Concurrent any longer.  The Avalon team will make one last release
of those projects with all the classes deprecated.  It will allow you
to maintain backward compatibility while pointing your users to
higher quality libraries that are maintained better.

Excalibur Collections has been merged into Commons Collections-2.1,
and as a result the class names have changed.  All the deprecation
messages point you to a compatible class.

Excalibur Concurrent has been stopped completely, and we are using
Doug Lea's Util.Concurrent library.  That is the library that will
perform the basis of the new JDK 1.5 threading primitives.  It is
in the public domain, so it should not pose any licensing issues
for anyone.

You will still have to include the JARs for projects outside the
scope of ECM's direct dependencies like SourceResolver which now
works in both ECM and Fortress environments.

If you can furnish a list of all the Cocoon dependencies to the
Avalon Developers list ( we can
incorporate them into the Excalibur Phase I release.

Your help will be greatly appreciated, and in the end will directly
help you.

            -- The Avalon Team.

To unsubscribe, e-mail:
For additional commands, email:

View raw message