On Sat, 23 Oct 2004 22:45:44 -0500, Eddie Bush <[EMAIL PROTECTED]> wrote: > Howdy Y'all, > > Just wondering how we wish to address bugs in things Struts is dependant upon, such > as validator, file-upload, etc. Should these bugs remain filed against Struts? It > seems more apropriate to me that they be closed with an FYI that the issue is with > something we're dependant upon and not with Struts itself, as well as a tactful > request that the filer go file against the project we're dependant on. >
If you're positive that the bug is in the external component, and not in the glue code for that in Struts, then you can change the Bugzilla product and component to that of the external component in question. (Be aware that this is a two step process - you'll need to change the product first, before you'll get the appropriate component list to choose from.) If there is some question about whether it's in the external component or in the glue, I think the bug should be left here until that is determined. -- Martin Cooper > Does that rub anyone wrong? Why? I'm curious about protocol here. > > Perhaps we should close the bug and file the new one on their behalf, including > their email on the newly-filed bug? > > Thanks! > > Eddie > > --- > avast! Antivirus: Outbound message clean. > Virus Database (VPS): 0443-3, 10/22/2004 > Tested on: 10/23/2004 10:45:46 PM > avast! - copyright (c) 2000-2004 ALWIL Software. > http://www.avast.com > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
