Rewriting scm urls when a tagBase parameter is present.

For example, I have a simple pom like this:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>org.jboss.maven.test</groupId>
<artifactId>maven-build-test-module1</artifactId>
<version>1.0-SNAPSHOT</version>
<name>Test Project</name>
<description>A project to test the release and packaging features of maven</description>
<scm>
<connection>scm:svn:http://anonsvn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk/</connection>
<developerConnection>scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk/</developerConnection>
<url>http://fisheye.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk</url>
</scm>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-5</version>
<configuration>
<tagBase>https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags</tagBase>
</configuration>
</plugin>
</plugins>
</build>
</project>

When I prepare a release, the URLs in the scm configuration are translated to the following:

<scm>
<connection>scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0</connection>
<developerConnection>scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0</developerConnection>
<url>https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0</url>
</scm>

The developer connection is correct because it is based off the tagBase, but the connection and url in this case are now pointing to the wrong place.
Maybe there should be separate release plugin parameters similar to tagBase, but used for setting the tag urls for scm.connection and scm.url.