On Mon, 21 Oct 2002, Nicola Ken Barozzi wrote:
> > [EMAIL PROTECTED] wrote: > >>>Therefor I still think Jakarta Commons should fix their naming scheme. > >>>But that will have to be brought up there, not here. > >> > >>It's completely impractical, and will hurt Jakarta immensely. > >> > >>Oh, well, now that I think of it, this is only for projects that have > >>already been released... > >> > >>Other opinions? > > > > Has everyone forgotten that it's not just commons that uses > > org.apache.<projectName> as their java package name within Jakarta. > > > Ant is org.apache.tools.ant > > Turbine is org.apache.turbine > > Velocity is org.apache.velocity > > Struts is org.apache.struts > > etc. > > Sure, and Turbine will get a turbine.apache.org site, Ant an > ant.apache.org site... but Commons? Bear in mind this is not just a website change. It breaks backwards compatibility of all jakarta projects [at least ones people code against] and will be confusing to users. > Why not just decide to move the Jakarta Commons projects to Commons and > the Sandbox ones to Incubator? Some of the Sandbox ones are blatant Commons projects which just aren't ready yet. I know that this is probably acceptable to the Incubator concept but wanted to make sure. Equally, when does something go from Incubator to Commons? In Jakarta it seems to be on release of a 1.0. Do things have to stay in Incubator until they have a 1.0 release? Hen -- To unsubscribe, e-mail: <mailto:general-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:general-help@;jakarta.apache.org>
