> Java jars are nto at all complex beast. They become tricky in situation where > you just put some of them inclasspath and they do what you normally do not > expect. Lib should be lib and when not called by developer they should do > nothing. Deliberatly breaking this rule makes the jars, beast ... :-)
Sorry, but that is b.s. Could you point me where this 'rule' is defined? You bet you can have troubles if you just mindlessly include all kinds of jars. Furthermore, what is your whole point of having to include jars you are not using? If you would be using them, you'd need those other dependencies, period. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
