On 4/23/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
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.
In the release notes, we listed several plugins and features that were considered "experimental", and the Tiles 2 plugin is among those. Realistically, the alternative would have been to withhold the Tiles 2 plugin from the Struts 2 release. Likewise, if we couldn't release the Maven artifacts because of the internal snapshot dependency on annotations, we probably wouldn't have had a release at all. As things are setup now, we could start releasing plugins independently whenever we choose, or mix and match. We could, for example, easily create a struts-tiles-plugins-2.0.7.1 release, if need be, and release it on its own. Each plugin has its own POM, we simply choose to distribute the artifacts together. The issues are social. People just don't want to deal with managing releases of 18 distinct S2 artifacts (literally). I don't know if Struts 1 would ever get to eighteen now, but if we had Struts 1 plugins three years ago, it certainly would have. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
