I'm not sure that this would be considerably different from how things are generally done anyway. A class added in JDK5 is expected to work in 6+. Granted there's not a different package for each Java release, but I doubt it would cause as much confusion as you think.
Actually, now that I think about it more, I wish Sun would use version numbers in its naming convention. Perhaps it's my COM background showing through, but it's exceedingly annoying how they just change interfaces. It is impossible to compile some SQL code on Java5 & Java6 due to interface changes in the same named interface. -- Kevin On 5/19/08 5:20 PM, "Markus Joschko" <[EMAIL PROTECTED]> wrote: > Looks like I am alone but I don't like the idea of putting version > numbers into package names. > In the highly unlikely case that there will be a tapestry 6 (not for > technical but solely for marketing reasons ;-)) it might confuse > developers. Are the classes in tapestry5 still valid or not? > > Only developers who will run tapestry4 and 5 in one webapplication > might have the problem of distinguishing between the packages. > I guess that they are the minority and it might be reasonable for them > to read the class comments if they are in doubt which package belongs > to which tapestry version. > > so -1 for a tapestry5 or v5. > > my 2cents, > Markus > > On Mon, May 19, 2008 at 9:58 PM, Blower, Andy > <[EMAIL PROTECTED]> wrote: >> I agree. >> >>> -----Original Message----- >>> From: Massimo Lusetti [mailto:[EMAIL PROTECTED] >>> Sent: 19 May 2008 16:02 >>> To: Tapestry users >>> Subject: Re: Instability in Tapestry 5.0.12-SNAPSHOT >>> >>> On Mon, May 19, 2008 at 4:57 PM, Howard Lewis Ship <[EMAIL PROTECTED]> >>> wrote: >>> >>>> The question is: would it have been better to just broadly rename >>>> org.apache.tapestry to org.apache.tapestry5? There was quite a bit >>> of >>>> discussion back on forth among the developers on this one. >>> >>> I would say yes. >>> >>> -- >>> Massimo >>> http://meridio.blogspot.com >>> >>> --------------------------------------------------------------------- >>> 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] >> >> > > --------------------------------------------------------------------- > 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]
