Hi there, I'm working on adding omitted nodes support to dependency-tree and have come across a limitation within DefaultArtifactCollector. The problem is when one node is omitted for conflicting with a nearer node and they have identical versions, i.e. they are duplicate nodes.
You can see in DefaultArtifactCollector.fireEvent for OMIT_FOR_NEARER, the event is only fired to listeners if the versions differ. Hence the event is never fired for duplicate nodes, which makes it impossible to accurately reflect what Maven is doing internally in the dependency tree. I'd like to remove this restriction to allow interested listeners to easily track duplicates. Has anyone got objections to me committing this change to 2.0.x and 2.1? Cheers, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
