>Ah, now I see what you mean. This does indeed look strange, especially >the wording of the message. On the other hand, it is just an INFO and >not a WARNING like the other problems found by the dependency:analyze >goal. I don't know if this behavior is intended. The message may be even >useful, because there may be something wrong in the project if a certain >dependency is excluded from one module but pulled in by another. If I >exclude it once it is very likely that I don't want it in my module at >all.
Hi, this is how it was intended to work. It's intentionally looking for anything you excluded somewhere to see if it crept back in through another avenue. See here: http://jira.codehaus.org/browse/MDEP-76 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
