On 9/6/05, Christian Meder <[EMAIL PROTECTED]> wrote: > How is "Struts Classic" related to this whole discussion ? > > IMHO Struts Classic describes the core component best. At least that's > the part with which I started doing Java web application development 4 > years ago so it's definitely the oldest part of the Struts framework.
The "Struts Classic" label is being used to describe a distribution of the six orginal subprojects, which includes Core: > Originally, the Apache Struts software was distributed as one > monolithic bundle. Today, the Struts project is comprised of several > subprojects. Each subproject has its own website, documentation, and > release cycle, and may be downloaded separately. The six original > Apache Struts subprojects -- Core, Taglibs, Tiles, Extras, > Applications, and EL -- are also being bundled into a distribution > known as "Struts Classic". The Core subproject does not include components like the Taglibs and Tiles. Experience proves that we *do* want to separate these components into separate subprojects. The "best available" version of each will be bundled as Struts Classic, as a convenient one-stop download. Then, if we want to bring out a fix or change in one component, we do not need to parade out all the rest. In the past, useful and stable improvements to one component have been "trapped" behind unstable improvements to another component, frustrating everyone. The subproject strategy will let us bring out improvements to one subproject without freezing development in other subproject . -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
