Re: Java package names
Benson Margulies <[email protected]>
| Newsgroups | gmane.comp.apache.incubator.river.devel,gmane.comp.apache.commons.general |
|---|---|
| Message-ID | <[email protected]> |
From the mentor standpoint, what's important to me is that there is no ASF requirement to change those packages. The community can decide to do it sooner, later, or not at all. The community can decide to make a slew of compatibility wrappers. The community, most importantly, can push toward a release with whatever naming it can reach a consensus on. On Tue, Oct 12, 2010 at 4:09 PM, Christopher Dolan <[email protected]> wrote: > I vote against such an incompatible change. There are a lot of classes under there, for example com.sun.jini.thread.TaskManager, that are utility code employed by downstream developers. I think all new code should go elsewhere if possible, but changing the existing com.sun.jini packages would be hard on existing users. > > Chris > > > -----Original Message----- > From: Benson Margulies [mailto:[email protected]] > Sent: Tuesday, October 12, 2010 11:51 AM > To: [email protected]; [email protected] > Subject: Java package names > > River imported packages of code from the original Sun grant under the > name 'com.sun.whatever'. > > How important is it to change that? >