If you are not using the whole branch of WICKET_1_2 as your development workspace for Wicket (shame on you!), but prefer to check out individual projects, you will find it hard to get the parent pom.
This next subversion statement will get you the parent pom, which you can then install into the local repo. svn -N co https://svn.sourceforge.net/svnroot/wicket/branches/WICKET_1_2/ A WICKET_1_2/pom.xml Checked out revision 6402. and then: cd WICKET_1_2 mvn install I'm still not convinced this is *the* way to go, however this does follow Maven best practices. Perhaps a project directory for the parent *next* to the wicket projects is a better fit. Packaging is also a problem, as the zips are not buildable using maven out of the box without installing the parent pom first (and I have to find a way to include the parent pom in each distribution), or until *we* publish the parent pom to ibiblio. The latter takes time as we don't have write access to ibiblio. Martijn -- Download Wicket 1.2 now! Write Ajax applications without touching JavaScript! -- http://wicketframework.org Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
