>I'm all for testing this more thoroughly for anything that might not be > spot on with the resolution but the process is that any transitive >dependency is aligned to the depMan section unless a dependency in a >child project overrides the version. I believe users would expect this >to be the behavior and has only resulted in making additions which is counter >intuitive. I think staging a release that folks can try this behavior would >be prudent. The desired behavior is now in effect but we should ferret out >anything but this patch has been used in production and if we can get 10-15 >largish production builds to try this I think we would be safe in releasing it.
I'm agreeing that this should be the default ;-) I have a very large build and will try this out once it's staged (maybe even sooner if I have time). I do know that I have some workarounds in place because of this. This new feature will make it safer to use the dependency-analyzer. Now I will know its safe to remove an unused direct dependency once I update my depMgt. Right now, I would have to remember that I put it there to override a problem. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
