"Jakarta Tomcat" was used in many contexts, and I don't see why a user would be confused - or care or know what a TLP is. That's internal apache organization.
My point is - it would be better to stop using jakarta for future, and not change the past. Tomcat5 was released as 'jakarta tomcat', and it's more or less history - we make sort of maintainance releases. For tomcat6 and other future releases - we can stop using jakarta. Costin On 6/28/06, Yoav Shapira <[EMAIL PROTECTED]> wrote:
Hi, On 6/28/06, Costin Manolache <[EMAIL PROTECTED]> wrote: > And why are you doing this ? Why are we doing the renaming? Because the relevant project is no longer part of Jakarta, so to avoid confusion among users, be consistent with other Tomcat code, discharge the Jakarta PMC from responsibility, etc. Ideally we would have done this right after we became a TLP, but better late then never. Or did you mean something else other than the renaming by "this" in the above question? Yoav > > For tomcat5 - I don't see how much it helps. For tomcat6+ - I think the > main issue is figuring where to put the native code so the duplicated > java source trees don't confuse people. Given how much unused native > we have, it may be good to just move mod_jk and whatever else is still > used to tomcat6/ repo. > > Costin > > On 6/28/06, Rainer Jung <[EMAIL PROTECTED]> wrote: > > > > I think it's time to rename jakarta-tomcat-connectors to > > tomcat-connectors. I'll try to handle the remaining jakarta-tomcat > > artefacts inside the connectors module and concerning the download. > > > > Does anyone know about external references we might break? > > > > Rainer > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- Yoav Shapira Nimalex LLC 1 Mifflin Place, Suite 310 Cambridge, MA, USA [EMAIL PROTECTED] / www.yoavshapira.com
