On 6/19/07, Watter <[EMAIL PROTECTED]> wrote:
This is no big deal to add, but out of curiosity, is this something new? Our builds have been running fine without this on all previous 1.3-SNAPSHOTs, and if it's a dependency of Wicket now, why is it not indicated in the Wicket pom? I assume it's because it might be different depending on which logging library one uses, but it is a little unfortunate that this technique kind of limits one of the nice benefits of using maven; automatic dependency resolution.
Yeah, as a bit of a stab at the maven folks, not you: contrary to popular belief, Maven doesn't allow one to turn of one's brain. When you work with dependencies *and* plugins one reallly needs to add all dependencies to the dependencyManagement part and explicitly tell maven which versions *you* want. Transitive dependencies are a nice thing, but they can bite you in the butt much harder than just plain old dependencies. 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
