Noel J. Bergman wrote:
What this means is that in addition to providing binary compatibility
with all your users, the deprecation messages from Javac will reflect
Cocoon deprecations.
How does this impact the changes requiring Stephen to convert CM to SM for
James? Or doesn't it?
SM is the direction of all future efforts. We want people to to migrate
to SM. However concerning the nature of the complaints from the Cocoon
crowd where they do specialized containers, we had to use a soft
deprecation so as not to unnecessarily scare their users.
Excalibur Concurrent has been stopped completely, and we are using
Doug Lea's Util.Concurrent library.
Are you exposing util.concurrent, or are you hiding it underneath? What
impact does this have on those of us using your threadpools?
It is largely hidden underneath. You have two choices for threadpools.
You can use the version in Excalibur, or you can use the version in
util.concurrent.
I am familar with d.l.u.c and JSR 166. I'm just concerned about short term
migration issues.
We do have the library available for those projects who cannot quickly
migrate. We do understand those issues. The Avalon team could not
provide anything as high quality as Doug Lea's library, nor could we
effectively maintain what we had. Our users deserve better. To
deliver, we need to focus on our competencies.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
