absolute file path in distributionManagement.site.url in sub project is made relative to parent site.url

I have attached a test case and a log file which illustrate this issue. Basically, the issue we are seeing is that we have two projects, "base", and "module" where module inherits from base and is a module in base. In base, we have the site being deployed via scp to one location. In the module, we have attempted to override the site to make it deploy to a local file. We did this so we can test the site locally deploying it to the real location. In our scenario, the module project is owned by another group, and they will ultimately want to deploy their site someplace else.

What happens is that when we run mvn site-deploy in the module project, instead of the site going to a file as we expect, maven actually attempts to upload it via scp. You can see from the log file that it is attempting to deploy the site for "module" via scp:

[INFO] — maven-site-plugin:3.0:deploy (default-deploy) @ module —
scpexe://www.example.com/1.0-SNAPSHOT/ - Session: Opened
[INFO] Pushing D:\temp\siteInheritanceBroken\module\target\site
[INFO] >>> to scpexe://www.example.com/1.0-SNAPSHOT/file:///c:/temp/my-site

This issue is hampering our ability to test the generation of our maven site. We have not tried deploying the module project to a different server yet.