On Sat, Mar 14, 2009 at 12:32 PM, Gary Gregory <ggreg...@seagullsoftware.com> wrote: >> -----Original Message----- >> From: Henri Yandell [mailto:flame...@gmail.com] >> Sent: Saturday, March 14, 2009 2:21 AM >> To: Commons Developers List >> Subject: [lang] 3.0, what's in; what's out >> >> Starting up a thread for cleanup discussions on Lang. > Thanks for taking the lead :) > >> >> I've removed the enum (was a blocker on JDK 5) and enums (people need >> to use real enums now) packages from Lang's trunk and moved them to a >> lang-backcompat sibling component. I've not made it a branch, it lives >> at the same level as trunk and will need its future to be decided. > > This is going to be painful for our team at work. We are in the process of > converting _some_ of our [lang] Enums to Java 5 enums but we will probably > not get around to fixing everything. Unlike migrating to chained exceptions, > migrating to J5 enums is not trivial. While our HEAD code has already moved > to Java 6, we are sitting on a huge pile of legacy code. It would be a shame > for us to be stuck on [lang] 2.x as we modernize the rest of our code with > generics and other APIs. So for now, keeping emums would help, perhaps in a > separate package? > > I suppose we could have both 2.x and 3.x on the classpath... Now that I think > about it, we might have to just to satisfy some third party dependency. Hm.
They're in the backcompat location. Someone with the itch will need to develop a build/release around it, but it's unlikely to be very hard. I didn't move deprecated things over. I also didn't move the NestableException code over. I'll get that branched over now as it seems like a likely backcompat desire. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
