I would love too. But what confuses me is the aim of wicketstuff projects.
Some of them seem to follow wicket release cycle, some have their own cycle, and always build against wicket-trunk. It would be helpful if wicketstuff projects have a clearer release cycle plan. Also some projects use release #s analogues to wicket i.e. 1.3.x and some use 1.0 and others 0.1 etc. Wicketstuff projects really could use a proper release cycle and numbering strategy. Martijn Dashorst wrote: > > or you could volunteer to build those releases for the wicket stuff > projects :D > > Martijn > > On Tue, May 20, 2008 at 3:35 PM, gumnaam23 <[EMAIL PROTECTED]> wrote: >> >> But then, the wicketstuff maven repository is never deployed with these >> builds following the wicket releases. >> Everything in the maven repository follows wicket snapshot. This is >> really a >> pain, I have to maintain a >> private wicketstuff code base, just to give the projects proper release >> #, >> and proper dependency on wicket releases, rather than wicket-SNAPSHOT. >> >> may be someone needs to introduce the "mvn deploy" command to the >> wicketstuff developers ;). >> >> >> >> Martijn Dashorst wrote: >>> >>> If you want your project to be used, I think it is wise to do so. A >>> higher release schedule is also nice, but lower seems to indicate a >>> bit of a dead end imo. >>> >>> Martijn >>> >>> On Tue, May 20, 2008 at 3:13 PM, James Carman >>> <[EMAIL PROTECTED]> wrote: >>>> So, is the philosophy of wicket-stuff that all of the projects kind of >>>> mirror Wicket's release schedule? >>>> >>>> On Tue, May 20, 2008 at 9:06 AM, Martijn Dashorst >>>> <[EMAIL PROTECTED]> wrote: >>>>> 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] >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> 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] >>> >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/-PROPOSAL--wicketstuff-SVN-reorganization...-tp17339733p17340319.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> 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] > > > -- View this message in context: http://www.nabble.com/-PROPOSAL--wicketstuff-SVN-reorganization...-tp17339733p17357868.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
