[regression] Plugin configuration incorrectly inherited from parent pom

Until 3.0-beta-1 this was working correctly, but now when I run release:perform, it runs the goals from the un-inherited plugin configuration instead of the one in pluginManagement that should be inherited.

In this example, the release plugin on the project should run goals: "deploy nmx-pom:dependency", but instead it is running "deploy nmx-pom:parent". The latter is what the parent pom project itself runs on release.

It seems that maven is now ignoring the <inherited>false</inherited> flag, at least in some cases.

This is confirmed by the effective pom as well (see below). Note that the effective pom in m2eclipse (that must still use the embedded maven instead of the external one I setup in Eclipse Preferences) has it correct.

The release goals are all setup by the parent pom, which contains this:
...
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-9</version>
<inherited>true</inherited>
<configuration>
<tagBase>http://svn/repos/libraries/java/$

{project.artifactId}

/tags</tagBase>
<useReleaseProfile>false</useReleaseProfile>
<!-- goals to run during release:perform (removed site-deploy from default settings) -->
<goals>deploy ca.nanometrics.maven:nmx-pom-plugin:dependency</goals>
<arguments>-Dpom.update.skip=$

{pom.update.skip} -Dhudson.url=${hudson.url}
-Dhudson.jobName=${hudson.jobName} -Dhudson.buildNumber=${hudson.buildNumber}</arguments>
</configuration>
</plugin>
</pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-9</version>
<inherited>false</inherited>
<configuration>
<tagBase>http://svn/repos/tools/maven/common-pom/tags</tagBase>
<useReleaseProfile>false</useReleaseProfile>
<goals>deploy ca.nanometrics.maven:nmx-pom-plugin:${nmx-pom-plugin.version}:parent</goals>
<arguments>-Dpom.update.skip=${pom.update.skip}

-Dhudson.url=$

{hudson.url}

-Dhudson.jobName=$

{hudson.jobName}

-Dhudson.buildNumber=$

{hudson.buildNumber}

</arguments>
</configuration>
</plugin>
</build>

The effective pom of the project itself, using 3.0-beta-1 has:
...
<plugin>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-9</version>
<inherited>true</inherited>
<configuration>
<tagBase>http://svn/repos/libraries/java/apollo-workstation/tags</tagBase>
<useReleaseProfile>false</useReleaseProfile>
<goals>deploy ca.nanometrics.maven:nmx-pom-plugin:dependency</goals>
<arguments>-Dpom.update.skip=false -Dhudson.url=
-Dhudson.jobName= -Dhudson.buildNumber=</arguments>
</configuration>
</plugin>
</plugins>
</pluginManagement>
<plugins>
<plugin>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-9</version>
<inherited>false</inherited>
<configuration>
<tagBase>http://svn/repos/libraries/java/apollo/workstation/tags</tagBase>
<useReleaseProfile>false</useReleaseProfile>
<goals>deploy ca.nanometrics.maven:nmx-pom-plugin:1.3.3:parent</goals>
<arguments>-Dpom.update.skip=false -Dhudson.url=
-Dhudson.jobName=
-Dhudson.buildNumber=</arguments>
</configuration>
</plugin>
...