All, I've updated the pom structure to maximize reuse in our poms.
in the root folder of the wicket 1.2 branch, you will find a pom.xml this is the parent pom. the parent pom contains all dependencies for the wicket projects including the correct versions. As we will be releasing the different projects as consistent packages with the same numbering scheme, this is a great way to get that consistency. To make it work, you have to 'install' the parent pom into your local repository. I'm still in limbo whether to put the file into a separate project directory or just to keep it where it is now. Maven seems to prefer the current setup. Everytime we update a dependency in the parent pom, you'll have to install it. This is extra work, but this will help us not having to fix all projects for an upgrade in a dependency. so: svn co https://svn.sourceforge.net/svnroot/wicket/branches/WICKET_1_2 and then in the root directory: mvn install this will install the wicket-parent-1.2-SNAPSHOT pom into your local repo, giving access to all other projects that depend on it. 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 Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
