2007/4/23, Paul Benedict <[EMAIL PROTECTED]>:
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.
Isn't it a problem of assemblying the artifacts? We've got the assembly plugin for this!
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.
I see your point, and you're right when you say that, when changing the base library, the depending items must change accordingly. But this process happens usually only in early development cycles, not when the base code is stabilized. What I don't want is to see another case of snapshot dependency. In the case of Struts 2 probably it was due to the lack of knowledge of integration package status: not all people knew, for example, that the dependency to Tiles 2 was to 2.0-SNAPSHOT, and it inadvertently went GA: what is happening is that some people are using Tiles 2 in a wrong (or better, old) way. When Struts 2 will depend on a stable release of Tiles 2, we must say: we are sorry, you have to change all your XMLs and JSPs. Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
