On 11/1/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > I haven't been a fan of the naming convention being introduced, and I've > said so in the past. But, as Ted points out in another post, no one, > including me, offered any better suggestions either, so it was just > pointless whining. Let me try and change to something more > constructive...
To summarize, * Instead of having a Struts Classic distribution, we could have a "struts-core-library" distribution instead, that could also include other Core compatiblity extensions, like Struts Flow and Struts Scripting. If we did, then "Struts Classic" would be relegated to a codename we used to get the "seven dwarfs" ready to ship. * Yes, in addition to a "struts-core-library", we could also have an "apache-struts-all" distribution that included all the subprojects in one bundle. In other words, it would be the GA version of the nightly build. (But first, we need GAs to bundle!) * Our "Struts Validator" is based on the "Apache Jakarta Commons Validator", which could become a top-level Apache project whenever the people working on the Validator wanted to go through the application process. (Ditto for Struts Tiles.) We don't see a way to break "Struts Validator" out from Struts Core, since the reusable functionality is already in the Commons package. As the rest: Yes, that sounds like what we are doing. :) -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
