Fair enough. I also like Hubert's idea of renaming the ticket and beefing up ModuleConfigVerifier to resolve it.
/me glances at the bug list...319 of these conversions to go. :) Side note, it is my personal mission to try to drastically reduce the number of both bugs and enhancement tickets against Struts. If folks took the time to get involved and write a ticket, the least we can do is give feedback if we'll solve it or not. I'd assume we won't be able to resolve all the tickets as some enhancements are valid, but we have no intention of implementing them ourselves, but if we could make those the rule not the exception, I'd feel a lot better about moving the project forward in new directions. Speaking of, aren't we about ready for a 1.3 release? IIRC, we were waiting on Hubert's extends patch. How's that coming? Are we about ready to roll? I'll volunteer to roll this release if no one else wants to. It's my first time, so be gentle :) Don Ted Husted wrote: > On the Roadmap for Struts Core, there's an entry where we consider > refactoring for Spring. Such a refactoring would be an excellent > opporunity to address issues like this. I'd suggest we mark this > ticket to handle during that iteration, and cross-reference the > Roadmap. > > Heck, if we switch to a wrapper around the Spring XML loader, than a > lot of this would be resolved. > > And, of course, we did address this ticket to some extent with the > config verifier. > > -Ted. > > On 4/21/05, Don Brown <[EMAIL PROTECTED]> wrote: > >>It may be a valid issue, but so is "Make Struts Faster". My point is >>this ticket is so broad its long life is a testament to its validity or >>lack thereof. I suppose it gets down to how each developer views >>tickets, but I personally see enhancements tickets as requesting a >>specific feature that can measurably be addressed. If this ticket was >>broken up into its specific examples, they'd be fine tickets I'd even >>recommend be marked bugs. >> >>I don't feel strongly enough to make a big deal of this, but it is >>another symptom of a general "paralysis" I feel affects Struts >>development. Sure, we need to be careful for backwards compatibility >>and we want to encourage participation, but there is also value in >>having a strong direction and making tough decisions to move the project >>forward. Three year old bugs so general they remain unaddressed, I >>feel, need to either be fixed or resolved in another manner. If we >>can't come to grips with our past, how can we lead in the future? >> >></sermon> :) >> >>Don >> >>Ted Husted wrote: >> >>>You might open a wiki page where we could start collecting more >>>information, and perhaps develop a strategy. >>> >>>IMHO, this is a valid issue. But, it's also an enhancement, and won't >>>block a release. Marking it invalid doesn't seem appropriate. >>> >>>-Ted. >>> >>>On 4/21/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >>> >>> >>>>DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· >>>>RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT >>>><http://issues.apache.org/bugzilla/show_bug.cgi?id=5739>. >>>>ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· >>>>INSERTED IN THE BUG DATABASE. >>>> >>>>http://issues.apache.org/bugzilla/show_bug.cgi?id=5739 >>>> >>>>------- Additional Comments From [EMAIL PROTECTED] 2005-04-21 16:55 ------- >>>>My concern with this bug is that it started out with a broad scope, and in >>>>the >>>>course of its life, became even more so. I wouldn't be opposed to reopening >>>>the more specific ones, and either marking this as invalid or renaming it to >>>>limit its scope to checking struts-config declarations. >>>> >>>> >>>>-- >>>>Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email >>>>------- You are receiving this mail because: ------- >>>>You are the assignee for the bug, or are watching the assignee. >>>> >>>>--------------------------------------------------------------------- >>>>To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>> >>> >>> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
