> (The following is a little off-topic for dependency-maven-plugin > specifically, but I think it needs to be said.) > > For an experience Maven2 user, the value of these docs is immediately > obvious. > > For the newbie, however, there is still the feeling: > > "OK, so now what do I do."
+1 (+2 if I could) a simple addition in the "About xxx plugin" generated file would do the trick. For example, if you see http://maven.apache.org/plugins/maven-site-plugin/index.html After the "Goals available:" table, simply add : "Configuration: To use this plugin, you will need to add to your pom : <plugin> <groupId>org.apache.maven.plugins</groupId> (is this necessary ? perhaps not for org.apache.maven.plugins, but for other like org.codehaus.mojo...) <artifactId>maven-site-plugin</artifactId> </plugin> For more information, see "Guide to Conguring Plug-ins" (link to http://maven.apache.org/guides/mini/guide-configuring-plugins.html)" I think this would really help the newbie : personally, for example, it took me a long time to discover that naming convention for Maven plugins was "maven-xxx-plugin", but for Mojo plugins it is "xxx-maven-plugin". Carefully reading the plugin documentation would have been sufficient, but... Is there an existing JIRA entry, or should I create one ? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
