You'll also want to build the plugin using plugin:install-now instead of plugin:install so that it is available to the current maven invocation.
- Brett > -----Original Message----- > From: Heritier Arnaud [mailto:[EMAIL PROTECTED] > Sent: Thursday, 27 May 2004 3:20 AM > To: Maven Users List > Subject: RE : plugin dependency > > > You can use a dependency for plugin like this : > > <dependency> > <groupId>statcvs</groupId> > <artifactId>maven-statcvs-plugin</artifactId> > <version>2.4</version> > <url>http://statcvs-xml.berlios.de/maven-plugin/</url> > <type>plugin</type> > </dependency> > > Arnaud > > > -----Message d'origine----- > > De : Glenn R. Golden [mailto:[EMAIL PROTECTED] > > Envoy� : mercredi 26 mai 2004 19:17 > > � : Maven Users List > > Objet : plugin dependency > > > > > > I have a multiproject system, and one of the projects is a > > custom maven > > plugin. One other project uses this plugin in its goal. > > > > I have been running the plugin project by hand, then doing a > > multiproject:goal for the rest. The reactor lists that > > plugin project, > > and places it last, since there are no stated dependencies on it. > > > > Is there a way to indicate in the project that uses the > > plugin that it > > is dependent on that plugin, so that the reactor will run it first? > > > > Thanks. > > > > - Glenn > > > > Glenn R. Golden > > CHEF Architect - Sr. Systems Research Programmer > > School of Information, Media Union - University of Michigan > > [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > > 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] >
