>I didnt quite understand this. depMngmt in plugins you use is ignored, >so how could you override a plugin dependency using this bug?
My understanding of the bug is that if you specify depMgt in _your_ project, it will influence the plugin's classpath. That means you could force a plugin to use a version you want by putting it in your depMgt. >other than that what's the overall consensus on fixing this for 2.0.9 >? I vote for fixing it Since we don't currently allow users to override plugin dependencies...fixing this without allowing plugin dep overrides would take away the back door. That's why I suggested we fix them both in the same release. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
