I would like to create a "compatibility" project for all the Excalibur projects that we do not any longer support. Things that are deprecated like Concurrent and Collections would remain deprecated, pointing to the replacement libraries. Things that are not deprecated like CLI and Naming would remain as they are, with the disclaimer that the Avalon team is looking for a good home for this code.
We would continue to provide bug fixes for any bugs that are reported against the compatibility library if the classes are not deprecated. Beyond that, we are not persuing further development, and the JAR is provided as a convenience for those who have users of their own to continue to support.
The Compatibility library will be the home of any library we no longer wish to directly support because it is not in Avalon's scope. We can place things here without worrying about replacement libraries. When someone steps up to the plate wanting to support those libraries in another location, we can deprecate the libraries pointing to the new location.
+1 from me.
As an initial set:
CLI, Collections, Concurrent, IO, *possibly* Naming
I have a directory structure set up (approx 250Kb) which shows what it would look like (xdocs not done):
http://avalon.apache.org/~bloritsch/compatibility.zip
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
