I would drop the version from the docs if you're concerned of it being out of date. I don't think we should worry about updating that page continuously if we change a version in the pom.
On Sun, Jun 7, 2009 at 4:17 PM, Barrie Treloar<baerr...@gmail.com> wrote: > On Mon, Jun 8, 2009 at 12:10 AM, Brian Fox<bri...@infinity.nu> wrote: >> The version in the pom is the locked down version for our plugins to use. >> The latest release plugin is 2.0-beta-9: >> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/ >> >> You can override that version in your pom if you are releasing a plugin...we >> don't update the parent every time there's a plugin release, it's not >> needed. > > I understand that, its the fact the documentation says > "Everything that you need to release has been configured in the POM > all Maven projects inherit from. The release plugin configuration > being used is the following:" > and then uses version -9 when the parent pom is -8. > > Either the documentation needs changing or the parent pom needs changing. > Or it can get ignored as the parent pom is going to change very shortly. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
