> i just wanted to express, that not anyone trying to build a webapp with wicket > is a maven expert or wants to become one (i don't want either).
Agreed. > so, when someone asks a question on dependencies, i find it somewhat 'rude' to > just come in with a comment suggesting 'maven can tell it, read the maven docs > and you'll understand all this'... Ok. I think I know Martijn well enough to know it wasn't his attention to give a RTF kind of answer, but rather - my hunch - a quick reply how anyone using this project might found out. Especially since Igor gave a proper answer an hour before Martijn did. > maven surely has brought structure into projects - and building wicket with > maven just worked for me out of the box. but if you look at all those projects > out there, there is the case that maven 2 can't build maven 1 projects, > dependencies are sometimes not resolved automatically and if hand-adding libs > you start getting trouble if you don't know maven in more depth. Yeah, it's certainly not perfect. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
