On Tue, November 1, 2005 11:02 am, Ted Husted said: > 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. :)
Yeah, what I wrote wasn't exactly revolutionary :) I like what you say here Ted, but in my mind I think there are really two different issues, although they are clearly intermingled, that should be talked about... The first is simply the question of what is the name of the project at large? Is it still Apache Struts? And then everything else falls underneath it? I ask this because I was confused whether that was the case, or whether Struts Classic was actually the new name or just the new name of the one combined distribution. This is the kind of confusion I would hope to avoid, and maybe it was just me in any case :) The other part of it is what you call the released artifacts. In that regard, I didn't like Struts Classic because of the connotations that go along with it. What you suggest above I think avoids that very nicely and still gives a solid description of what the artifacts really are. That still allows you to have true sub-projects like Struts Ti, Struts Shale, etc. But then they are pretty clearly demarcated from the "main line", so to speak... It wouldn't confuse anyone about what Struts is, and also serves to show what Struts could become later. And at some point, when that major revolution comes around, then the Struts Classic moniker for what we now call Struts makes good sense. I wasn't aware of the points you made about Validator Ted... are you saying that the Commons Validator has been altered in such a way that it can no longer be separated from Struts? Or did I not understand your comments? > -Ted. Frank > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
