Thanks very much all for your helpful replies. I'll try to answer all at once:
Josh, I'm using Hibernate 3.5.6-Final. I'm going to clean out my .m2 repository of the Hibernate stuff, then try Bas' suggestion and see if it works without me having to manually install the jars to my local repository as I've done. Martijn, that sounds like a good suggestion in a sense, but I'm honestly trying to keep things as simple as possible (for future maintainability given I might not be the one working on this project next year), so hopefully I'll be able to get a pom.xml file together that does everything necessary without needing any local manager. But that's a good idea for my own stuff (i.e., at home) so I might give that a try. Thanks. Sebastian, just yesterday I tried letting Eclipse manage my dependencies using Maven (since this project uses Maven) and it seems sensible enough, just a different process and place to look to manage my external libraries. Thomas, prior to this project I used Ant exclusively, so that kind of thing is certainly the way to go, and it scales fine to lots of jars. You can get pretty tricky with Ant, and it's great for managing the jar/war metadata, signing jars, etc., lots of things I don't know how to do in Maven (assuming they call can be done -- this remains to be seen). Don, I've been tempted to looking into Ivy for a long time, and if it weren't for the fact that the Wicket project seems pretty Maven-centric (even acknowledging that they state that Maven is not strictly required), I'd probaby go back to Ant and use Ivy for my dependencies. I still may in the end. As I mentioned above, there's things I know how to do in Ant that I may want to accomplish without having to learn how in Maven. I still think Ant is pretty amazing really. With Ivy it might be a complete solution for me (I'm not one to use new software just because it's a popular fad, unless it's actually an improvement over what I'm already doing). Finally, thanks Nino, it turns out that I actually did use an archetype to generate the beginnings of this project, which is certainly one thing in Maven I do like. Postscript: I added the maven repository as suggested by Bas, backed all the Databinder stuff back to 1.3.0 so that I didn't need the SNAPSHOTs (and thereby fixed a bug due to a class that is no longer used), and stopped trying to use AuthDataApplication as my base class (using just DataApplication) since I'm using wicket-auth-roles and already had my own role-based auth classes in place. So now it works and has Hibernate and Databinder in the app. Next step: start building the database classes. Thanks all, this was very helpful. Ichiro --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
