hi eelco, > Maven is not rocket science imho, but if you loath the project, that's > fine as you don't have to build the project from source to start with > (unless you run a patched version). You can get versions and snapshots > from our server: > http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3.0-SNAPSHOT/
you got me wrong on this. i build wicket with maven without any trouble from svn. i'm fine with it. 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). 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'... 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. to make a long story short: maven is fine if the project is setup and maintained for it. else it gets a real pain. regards, --- jan. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
