Hi all, I have to agree with Andrew here. One year ago, JEE5 server were still scarce or underused, thus supporting the maintained two branches argument, but now is no longer the case and splitting efforts between two code bases doesn't sound most efficient.
Regards ~ Simon On Fri, Jun 20, 2008 at 11:00 AM, Andrew Robinson < [EMAIL PROTECTED]> wrote: > JSR 252 (JSF 1.2) was finalized on 2006-05-11 > Java 1.5 released 2004-09-30 > > I don't mind people maintaining JSF 1.1, but I do think that there is > very good cause to have 1.1 moved to branches and the latest JSF > specification as the trunk for each project. Over 2 years is plenty of > time to adopt JSF 1.2. If you choose to stay on an old API, there is > just cause to not have the latest and greatest code available. For > those that wish to stay on and support 1.1 on a branch, that is > perfectly fine, but I think it is time to stop burdening every > developer with supporting legacy code without just cause. Other > technologies support the latest, and I think 2 years is plenty of > notice to users. > > My $2 (gas price inflation from cents to dollars) > -Andrew > > On Fri, Jun 20, 2008 at 3:14 AM, Mario Ivankovits <[EMAIL PROTECTED]> wrote: > > simon schrieb: > >> In other words, keeping one line of code makes sense (less > >> maintenance) even if we lose some JSF1.2/JSF2.0-specific features or > >> performance boosts. > > > > While I second the rest of your mail, I wont do so with the sentence > above. > > > > We are developers, and, at least in your younger years ;-), you'd like > > to keep up with technology > > and use the newest things. And JSF 1.2 is anything else then new today, > > not to speak about JSF 1.1. > > In contrast, we spent alot of time to make our JSF 1.1 development > > upward compatible. > > > > I don't think that we are responsible to provide a vital community > > around a library > > which itself depends on a stone old architecture. > > > > So, yes to one line of code, but I'd like to see the bundle > > Tomahawk+JSF1.1 frozen. > > Anything new should go to a JSF 1.2 native Tomahawk. > > And JSF 2.0 release date + (lets say) half year the same should count > > for Tomhawk JSF 1.2 then. > > > > Ciao, > > Mario > > > > >
