Gang,
I would like to propose that we work towards an Avalon Framework 4.5 Release, with the following 'features' included;
* AvailabilityAware interfaces (proposed (CTR) last week) * JDK 1.5 compatibility (4.2 doesn't compile on Java2 ver 5 ) * Bug fixes, like the equals()/hashCode() I encountered recently. * Move to a single "avalon" top level group, and use "avalon/framework" * Other?
* Remove deprecated stuff to simplify the package.
Considering the additions, I think "4.5" is a reasonable increment. WDYAT?
With a 4.5, it would be a good opportunity to remove the deprecated stuff--it is a big enough of a jump.
Focus on simplifying--adding more is not the best thing because framework is complex enough as it is. If interface X is implemented, do Y. Etc. Etc.
--
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."
- Rich Cook
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
