On 4/22/07, Ted Husted <[EMAIL PROTECTED]> wrote:
On 4/22/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote: > If all integrations were projects on themselves, this would not happen. > This is due probably to the fact that Struts 2 did not use the Maven > release plugin, and I think that we need to use it since it forces us > to follow the correct way of doing releases. In Struts 1, we tried breaking it down and giving each major artificat its own release series, but people complained that it made the release process too complex, and there would be too much bookkeeping in keeping track of which plugin release went with which core release. So, we decided to lump everything together, Spring-style.
I totally agree, even to this day, that breaking out Struts 1 modules into independent releases is a bad idea. Why? Because it's essentially the framework spread across separate jars, and those truly have tight cohesion. Usually a significant upgrade in one library requires an upgrade of the rest. So I believe it was a mightily good decision to keep them all together as one version. With that said, the cohesion between the Struts library and integration libraries are less so. I do not object to separate release cycles with we had a s1-extras or s1-integration (or whatever) project. That would be the best of both worlds. Paul
