On 06 Sep 2007 17:23:13 +0200 (CEST), Robo <[EMAIL PROTECTED]> wrote: > And why not? Besides that Wicket is doing some initialization of not used > libraries is there any restriction of not including not neccesary libraries > in classpath? Most time I develop someting I have many libraries in my > classpath even if I do not use them ...
Because you seem to be running into trouble with your dependencies. If you include wicket-velocity, you need Velocity (which you could have guessed from the name of the project) and any dependencies Velocity has. If don't include wicket-velocity, you don't need Velocity. It's that simple. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
