Following on from https://issues.apache.org/jira/browse/BSF-32:
I'm not sure it really makes sense to include a single jar with all the BSF engine factories in it. For one thing, why would one want so many factories present? They will only work if the corresponding engine jar is also present, so most of the factories will fail at run-time. Another problem is the possibility of clashes between factories for different versions of a scripting language. The BSF3 code is still useful for Java 1.4 and Java 1.5, and the bsf-utils jar can be used with Java 1.6+ as well. == I'm also not sure that the specific engine test cases add much value - any failures I've seen are nothing to do with the BSF api code itself, but all about how the test classpath is set up. I think one could keep one or two of the test modules only. These should probably depend directly on the specific engine factory rather than on the bsf-engine bundle. Thoughts? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
