Hi Ruel, I believe a workaround is to include the dependency in the first antrun plugin instance encountered. one way to guarantee would be to include this in the root project.
I've included this comment in the issue for future reference - let us know how it goes. - Brett On 1/5/06, Ruel Loehr <[EMAIL PROTECTED]> wrote: > I have also run up against the bug filed in jira under MNG-1323. > > http://jira.codehaus.org/browse/MNG-1323 > > The basic issue is that in a multi-module build, for child modules, > plugin dependencies are not always resolved. > > I'm trying to come up with a workaround, but haven't yet come up with a > successful way of doing it. In this case, I need to write a jacidl > plugin, but how would I get the jar (a dependency) on the classpath for > this plugin to execute? > > > The original pom snippet is below: > > > > <plugin> > <artifactId>maven-antrun-plugin</artifactId> > <executions> > <execution> > <id>jacidl</id> > <phase>process-resources</phase> > <configuration> > <tasks> > > <taskdef name="jacidl" > classname="org.jacorb.idl.JacIDL"/> > > <jacidl srcdir="${basedir}/src" > destdir="${basedir}/output/gen-src" > includepath="${basedir}/output/idl" > > includes="**/TransactionService.idl,**/SASCurrent.idl"/> > > > </tasks> > </configuration> > <goals> > <goal>run</goal> > </goals> > </execution> > <!-- this plugin will need the jacorb jar as a dependency > --> > <dependencies> > <dependency> > <groupId>jacorb</groupId> > <artifactId>idl</artifactId> > <version>2.2.2.jboss.patch3</version> > </dependencies> > </plugin> > Ruel Loehr > JBoss QA > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
