With that proposal it is very hard to upgrade a version of a project to a newer version of Wicket. Each maintainer has do create and maintain the branches. Currently we split off the projects in one go when we upgrade Wicket.
In an ideal world all projects are constantly rebuilt when Wicket has an update in core (for a lot of projects this is already the case with our new teamcity), so maintenance on each project would in most cases require ensuring api compatibility. Martijn On Tue, May 20, 2008 at 2:59 PM, James Carman <[EMAIL PROTECTED]> wrote: > All, > > I was looking at the structure of the wicketstuff.org SVN repository > today and I came up with an idea. Currently, the > wicket-persistence-template project is located at: > > http://wicket-stuff.svn.sf.net/svnroot/wicket-stuff/trunk/wicket-persistence-template/ > > So, all subprojects sort of hang off of the trunk of the root > "wicket-stuff" (should we rename that "wicketstuff"?) trunk. It would > seem to be better if we let each subproject have their own > trunk/branches/tags triad like this: > > http://wicket-stuff.svn.sf.net/svnroot/wicket-stuff/wicket-persistence-template/trunk > http://wicket-stuff.svn.sf.net/svnroot/wicket-stuff/wicket-persistence-template/branches > http://wicket-stuff.svn.sf.net/svnroot/wicket-stuff/wicket-persistence-template/tags > > What do you think? > > James > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.3 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
