Alexey N. Solofnenko wrote:
Classpath ordering is a usual practice that is used, for example, for patching.
yes, and it doesnt work with signed JARs. And, because <fileset> doesnt impose an order, you can't guarantee the order of use.
The same classpath order could be used in debugger too. In our
case it could be hidden inside launcher. But there are other ways to achieve the same - for example, factories that can return Java6 specific FileResource, but it is cumbersome: (FileResource)project.createObject("org.apache....FileResource"). The later has its advantages too - project could configure the class to support permissions or not.
Facades, all you need are facades. More indirection.
This follows to settings. I think we could put the settings in the project class (as get/set methods or somehow else) - support or not permissions, old/new behaviour is not a property of the environment, but it is a property of a specific build script.
hmmm. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
