That sounds like a good plan for this release. add ".disabled" to the end of the lib names and have an enable/deploy script in each extension bin directory to rename it to the correct name ... along with associated doc of course.
Cheers, On 18/10/06, Andrew Borley <[EMAIL PROTECTED]> wrote:
Hi All, There is an issue with the SCA extension loading mechanism at the moment due to how we do a simple search and load of any libraries in the extensions directory. This can mean we see problems like TUSCANY-868 where users see errors or pop-ups when a library is loaded but it's dependencies don't exist (e.g. the python extension library on a system where python is not installed). These errors are harmless, but will make new users think that things are failing, which is bad. For the M2 release, I propose we ship with the ruby and python libraries renamed to something that doesn't end in .dll or .so and add some deploy.sh or deploy.bat scripts that simply rename these libraries to the right thing. This mirrors the ws service extension, as there are deploy scripts here to place the libraries in the right places under Axis2C. In the longer term, I guess we need to have some kind of extension metadata to define whether an extension is enabled or not. Any thoughts? Better ideas? Cheers Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Pete
