Re: [vote] Release 1.4 with only generics and stop support for 1.3

> [X] +1, Wicket 1.4 is 1.3 + generics, drop support for 1.3 Just for the record... /Gwyn

wicket-contrib-groovy update

(looks like the sourceforge wicket-stuff mailing list has been shut down? reposting here) Hi There. I'm also interested in this project, and I've started to update it. I've already got it compiling against wicket 1.3.2 and the maven infrastructure working with the latest m2eclipse plugin. Nest

Re: [vote] Release 1.4 with only generics and stop support for 1.3

-100 (oh no i mean this is the 100st mail) +1 then for generics withing a few weeks and 1 or 2 extra 1.3.x releases johan On Fri, Mar 21, 2008 at 10:01 PM, Timo Rantalaiho <[EMAIL PROTECTED]> wrote: > [x] +1, Wicket 1.4 is 1.3 + generics, drop support for 1.3 > > On Mon, 17 Mar 2008, Janne Hie

Re: [vote] Release 1.4 with only generics and stop support for 1.3

[x] +1, Wicket 1.4 is 1.3 + generics, drop support for 1.3 On Mon, 17 Mar 2008, Janne Hietamäki wrote: > Tell your clients Sun is EOLing 1.4.. And tell IBM to do the same with their 1.4 JDK. Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oyhttp://www.ri.fi/ >

Re: Planning Wicket Next Generation

are you mad? *VSS!!!* On Fri, Mar 21, 2008 at 5:33 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > mercurial! > > -igor > > > On Fri, Mar 21, 2008 at 4:39 AM, James Carman > <[EMAIL PROTECTED]> wrote: > > On 3/21/08, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote: > > > And other than that, I serio

Re: Planning Wicket Next Generation

mercurial! -igor On Fri, Mar 21, 2008 at 4:39 AM, James Carman <[EMAIL PROTECTED]> wrote: > On 3/21/08, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote: > > And other than that, I seriously doubt it's the VCS that's the issue, > > but rather it's supporting 3 (or more) different branches, testin

Re: Planning Wicket Next Generation

On 3/21/08, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote: > And other than that, I seriously doubt it's the VCS that's the issue, > but rather it's supporting 3 (or more) different branches, testing that > the patches work accross all branches, making different patches for > those that don't etc

Re: Planning Wicket Next Generation

And other than that, I seriously doubt it's the VCS that's the issue, but rather it's supporting 3 (or more) different branches, testing that the patches work accross all branches, making different patches for those that don't etc. With a relatively small team of *volunteers* it's a choice wher

Re: Planning Wicket Next Generation

Yes it was quite fascinating to watch him talk I don't want ti high jack the thread, but maybe have a look at http://www.youtube.com/watch?v=8dhZ9BXQgc4 this talk about git by one of the other main dev's , it's much more informative about how git actually works. don't let linus's talk keep yo

Re: Planning Wicket Next Generation

> > and don't even get me started on the talk you mentioned... > to make this clear: the talk is held by Linus Torvalds and most of the time he's bitching about how bad CVS is and how stupid the SVN guys are (with SVN devs sitting in the audience) for trying to fix something which is inherently br

Re: Planning Wicket Next Generation

unfortunately that's not possible, since we rely on ASF infrastructure, which is SVN. and don't even get me started on the talk you mentioned... Gerolf On Fri, Mar 21, 2008 at 11:33 AM, Antony Stubbs <[EMAIL PROTECTED]> wrote: > > Switch your vcs to http://git.or.cz/ git ( > http://www.yout

Re: Planning Wicket Next Generation

Switch your vcs to http://git.or.cz/ git ( http://www.youtube.com/watch?v=4XpnKHJAok8 intro ), then merging won't be a problem. Johan Compagner wrote: > > But doing a 1.4 release so quickly with only generics means for me > merging of 3 branches. -- View this message in context: http://www.