+1. We need to come up with a standardized way of dealing with this though I think. At first I didn't like changing package names, but it does help avoid the "jar hell" issue.
On 12/13/07, Mario Ivankovits <[EMAIL PROTECTED]> wrote: > Hi! > >> - go for 1.5 > >> - take advantage of generics > > +1!!! Frankly speaking this is probably applies to most of commons. > > > > If commons wants to stay relevant and not become just legacy we also > > need to take some steps forward. > +1 ... long overdue .... maybe too long!? > > Ciao, > Mario > > > --------------------------------------------------------------------- > 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]
