I do see benefit in having the struts-taglibs (and actions) being their own release because there are some very minor enhancements that don't really require a new action framework release. For instance, Struts 1.2.5 added the errorStyle and errorStyleClass attributes, which probably could have been released faster if they were separate. This is the same situation for the struts-actions library which doesn't need a framework upgrade to add new functionality.
However, the biggest downside of separate releases, as I see it, will be the confusion in the separate versioning of the libraries. Someone might be asking one day, "Does taglibs-1.3.11 go with struts-action-1.3.4 or struts-action-1.3.6?" It is really going to be difficult to eyeball which version library depends on which version library of another. Did I get this wrong? Isn't this how the independent libraies will be released at different schedules? If so, an alternative would be to re-tag all libraries and release them under one distribution version. If struts-taglibs go through 5 quick releases, that's also 5 quick releases of Struts too. Paul __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
