Add <dependencies> element to your plugin configuration to extend/override the plugin classpath. Please note this works fine only on maven 2.0.9
2008/7/31 Christian Schuhegger <[EMAIL PROTECTED]> > Hello, > > I just ran into a problem where I used the castor maven plugin as described > here: > http://www.castor.org/srcgen-maven-plugin.html > > I assumed that a plugin would use the same classpath as the project itself > where I included castor 1.2. But I seems as if a maven plugin operates in > its own classpath. I used the version 1.0 of the above plugin which uses > castor 0.97 and therefore the source generator did not produce a hashcode > method that new versions will produce. > > Is it somehow possible to manipulate the classpath of a maven plugin, e.g. > via exclusions and additional dependencies, so that a newer version of > castor could be "injected"? > > I will have the same problem with the idlj-maven-plugin: > http://mojo.codehaus.org/idlj-maven-plugin/index.html > which still uses a very old version of jacorb. This plugin seems to be > abandonned: > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=11698&fixfor=-1 > > I expect that most of these plugins will still work with newer versions of > the jars they depend on, because the source code generator will normally not > change its external interface. > > Thanks for any clarifications, > -- > Christian Schuhegger > http://www.el-chef.de/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
