-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm not 100% sure when I say this, but you should NEVER need to specify a plugin as a dependency of a project. It will not be bound into the build lifecycle, and cannot be configured here...in short, it's not seen as a plugin, but as a compile-, run-, or test-time dependency ONLY. See MNG-361 for more info (http://jira.codehaus.org/browse/MNG-361).
- -john J. Matthew Pryor wrote: > What are the practical differences of specifying a POM dependency of type > plugin > > <dependency> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-compiler-plugin</artifactId> > <version>1.0-alpha-2-SNAPSHOT</version> > <type>plugin</type> > <scope>WHAT WOULD GO HERE</scope> > <dependency> > > vs. a plugin entry in <build/> > > <build> > <plugins> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-compiler-plugin</artifactId> > <version>1.0-alpha-2-SNAPSHOT</version> > <configuration> > <source>1.5</source> > <target>1.5</target> > </configuration> > </plugin> > </plugins> > </build> > > I assume configuration cannot be specified in a plugin dependency > When will a new plugin or a new version of a plugin get downloaded & > installed? > When will the classpath be affected? > Does one imply the other? > > Thanks for any clarification > > Matthew > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFCb88RK3h2CZwO/4URAhzXAJ9JFuSWvelRS6NoOJQR64nFlWj6dQCggfs9 LgySSVeWSj82/ZQYbQOxR0c= =dvIf -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
