On 6/10/07, Al Maw <[EMAIL PROTECTED]> wrote:
Sure. We can't exclude commons-logging, as it's a genuine dependency for their code, so to do so would be wrong. But we can fix their non-optional compile-scoped dependencies on servlet-api, log4j, logkit and avalon.
There is still one problem in our examples: we statically bind to commons-logging (the spring examples still use it). That should be fixed too, perhaps not now, but in the near future.
I've done so in the dependenciesManagement section, which hopefully should work. Let me know if it doesn't.
It should work in my opinion (haven't tried). Thanks! Martijn -- Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org
