I have a library which I'm producing that will be used by other projects here. Now, I have some transitive dependencies that depend on two different versions of commons-collections, for instance. What is the best way of handling this for something that will be a dependency for other projects? Should I try to set explicit exclusions or should I use a top-level dependencyManagement entry?
-- Dan Adams Software Engineer Interactive Factory 617.235.5857 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
