Many maven plugins are wrapper around other tools. The plugin is designed for a version of the tool, and in many case user will want to use a specific version without having to patch the plugin. The <dependency> element on plugin configuration is a common way to do this, by overriding the plugin POM dependency with another version.
<version>VERSION OF CASTOR I WANT TO USE FOR CODE GENERATION</version>
This used to work with maven < 2.0.8
In maven 2.0.8, this doesn't work anymore as the <dependency> set in plugin configuration is added to plugin classpath, as a duplicate for the one declared by the plugin but LATER in the classpath (but I may be wrong on this analysis).
|<dependency> in plugin configuration doesn't override maven-antrun-plugin classpath||Closed||Unassigned|