How about: 3) ony check the artifact/types/artifact-version.type part of the overall file name?
On Wed, 5 Jan 2005 11:44:38 -0200, Felipe Leme <[EMAIL PROTECTED]> wrote: > Hi James, > > On Wed, 5 Jan 2005 12:18:41 +0000, "James Richardson" <[EMAIL PROTECTED]> > wrote: > > > 1.6.1 still outputs 20 lines of text for each component...but I don't > > understand quite what it is trying to achieve.. (Is that because case > > problems don't happen if you develop on linux?) > > It tries to solve a particular problem, as reported on MPEAR-9 > (http://jira.codehaus.org/browse/MPEAR-9). > > Unfortunately, the fix seems to be causing more problems than it solves. So, > there is currently another issue (http://jira.codehaus.org/browse/MPEAR-35) > that I'd like to use to provide a final solution for the problem (I haven't > done it yet because I was "off-line" for almost 3 weeks). We have 2 options: > > 1.Undo the checking > 2.Add a property that, if set, would cause the plugin to ignore the warning > > Option 2 would solve the problem, at the cost of requiring the users to set > the property after they got the warning for the first time (the warning would > explain that this warning might be normal and hence they should set the > property). But if the original error seldom happens, than we better implement > option 1. > > I'm more biased to implement option 1, as I think the original error is > pretty rare. > > Any suggestions/thoughts? > > -- Felipe > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://www.multitask.com.au/people/dion/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
