But when a component can't be used with a recent Wicket release, there is little or no use for it IMO.
I like the fact that many folks have contributed to wicket stuff, but I think there is little reality in giving each project its own release cycle. Though for popular javascript libraries such as prototype, scriptaculous and jquery it may be beneficial to have release cycles that follow those projects as well, I think that most libraries could benefit of at least being compiled against the latest current wicket development version, and given a cut-off when a new Wicket release has been created. But that is my vision for wicket stuff. I hope to give some sweet loving care to those projects someday, in the form of downloadable releases, and proper release management to the central repository. But I have to release a book , and take some time off after that before I can commit any time to this. Martijn On Tue, May 20, 2008 at 3:33 PM, James Carman <[EMAIL PROTECTED]> wrote: > So, the aim is for all wicketstuff projects to stay up-to-date with > the current wicket release, correct? I was thinking of wicketstuff > kind of like Apache Commons, a grouping of useful, self-contained > projects (that just happen to all be based on Wicket). The way we > handle upgrading across commons is to make changes to the parent pom > and release that. Projects wishing to use the newer version have to > upgrade in their poms. > > On Tue, May 20, 2008 at 9:16 AM, Martijn Dashorst > <[EMAIL PROTECTED]> 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] >> >> > > --------------------------------------------------------------------- > 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]
