> > Read the maven documentation and understand the pom. > > That's definitely something I don't want to do. It has become harder in a not > so > small number of cases to build things from source since there are different > and > incompatible versions of maven - even more so since some maven repos don't > seem > to exist any more (try building jpox from source drove me mad!). I for one > stick > with ant.
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/ I don't think everyone in the world will ever agree on ant vs maven. I for one think that for all it's shortcomings, maven introduced a lot more uniformity. I *hate* those projects where you have to spend hours figuring out how they set up their project structure and custom build file, and then figuring out how to best import it in your IDE. And then 80% of the time you have no clue about the versions of dependencies you're using as many projects that use ant simply don't provide that. Anyway, it's one of these topics... we decided on maven very early on in this project, and we're reasonably happy with it. If you need a customized build (if you are running a patched Wicket version), you can generate an ant file using maven, and depend on that from then on. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
