Specifically the following jars are no longer accessible to application by default;
excalibur-thread excalibur-threadcontext excalibur-pool excalibur-collections excalibur-instrument excalibur-logger excalibur-util excalibur-extension excalibur-concurrent
Does this mean that every application that, for example, wants to log needs to include the excalibur-logger jar? Also, could you again explain the "versioning problem" that you are trying to solve? I haven't understood it.
I'm not sure if I understood you correctly, but if this means what I think it means, then this change is IMHO not feasible for an application server. Imagine 100s of applications running under Phoenix, all including the same JAR - this is a waste of memory. Also, it is update hell, when you have to rebuild and redeploy every single application.
The right solution would be to let users make the choice, like it is now, instead of limiting them. I thought it was a great feature that I could put libraries in phoenix/lib or in the SAR file - why take that feature away?
Ulrich
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
