svn commit: r381398 - /maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-registry.apt

[jd...@apache.org]

Author: jdcasey
Date: Mon Feb 27 09:56:55 2006
New Revision: 381398

URL: http://svn.apache.org/viewcvs?rev=381398&view=rev
Log:
Adding warning to inform users about the flakiness of the plugin registry.

Modified:
    maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-registry.apt

Modified: maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-registry.apt
URL: http://svn.apache.org/viewcvs/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-registry.apt?rev=381398&r1=381397&r2=381398&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-registry.apt (original)
+++ maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-registry.apt Mon Feb 27 09:56:55 2006
@@ -16,6 +16,22 @@
   are various ways to configure or bypass this feature, and the feature itself
   can be managed on either a per-user or global level.
 
+* <<Warning!>>
+
+  The plugin registry is currently in a semi-dormant state within Maven 2. This
+  is because it has been shown to have some subtle behavior that is not quite
+  intuitive. While we believe it's important to allow the user to pin down which
+  version of a particular plugin is used across all builds, it's not clear that
+  this type of information should be machine-specific (i.e. tied to something
+  outside the project directory).
+
+  Users should be cautious when attempting to use the <<<plugin-registry.xml>>>.
+  Redesign of this feature in upcoming 2.1 and/or 2.2 is likely.
+
+  For now, Maven <should> keep using the same version of a plugin - assuming a
+  different version is not specified in the POM - until the user chooses to run
+  with the <<<-U>>> option explicitly enabled.
+
 * A Tour of plugin-registry.xml
 
   The plugin registry file (per-user: ~/.m2/plugin-registry.xml, global: