On 11/3/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > > This way it's always clear which distro a none-core subproject release > > works with. > > (i.e. you can't be sure about using taglib-1.3.1.2 with core-1.3.0, > > but you're sure that taglib-1.3.0.4 will work) > > I like this. 1.3.1 does not necessarily mean that it has improvements > over 1.3.0.15. It just means, that it was retested with 1.3.1 core.
Yup. And it gives us something to base another distro on. > But Hubert, seems that your naming convention about Core being _part_ > of distro will not fly. Well, the distro is for those who like one download that does what the 1.2.x downloads do. That'd be core + taglib + tiles + apps etc. It'll be like the Ant download. > P.S. I see nothing wrong with Classic. It calls things what they really are. To me it's a matter of perception. Struts Classic makes me think "the version you can still use if you don't want the newer version with the newer architecture". Kinda like tomcat 5 vs. tomcat 5.5. We don't have a Struts.Next yet. Once we do, then let's call the current codebase "Classic". Otherwise it's just misleading. IMO. > Michael. Hubert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
