Seems to me like the problem will only affect windows development, and then only if the user is lazy with capitalisation.
Requiring all users to set a flag to ignore the spurious error that this check generates seems counter-intuitive. In addition, the warning is completely over the top. At most it should be one line. My suggestion would be to: * check only that the artefact name (not including the path) matches what is expected, and then only if a flag is set. * raise a bug with the repository handling code to make sure that dependencies are case sensitive, as Java is case sensitive, even if windows is not. * make an occurrence of this condition cause a build failure when enabled. Cheers James --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
