On 9/14/05, Laurie Harper <[EMAIL PROTECTED]> wrote: > Sure; maybe some of the testing burden can be mitigated through unit > tesst (not sure if Struts has the infrastructure in place to unit test > custom tags?)
James Mitchell setup some automatic tests for the taglib, though a lot of the behavior is still tested through the tag-exercises application. Niall is correct. When I've applied taglib patches, the bullwork is always setting up tests that first prove that there's a problem, and then prove that the patch fixes it. With tags, a tricky thing is deprecating side effects, like, as Nial mentions whether content is trimmed to an empty string. But, if we had a process for doing that, such behavior could be deprecated and removed like any other. We just need to give people fair notice that change is afoot. -T. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
