Rendering the site produces a Fatal error message if the parent pom isn't in the parent directory

Apache Commons's parent pom[1] used by the 30+ commons components[2] is not in the parent directory. With maven 2.2.1 this just produces an [INFO] message saying "Unable to load parent project from a relative path". With maven 3 (built today from subversion) there is now also a [FATAL] message in the output (the build doesn't fail - but seeing [FATAL] in the output doesn't look good):

• [INFO] — maven-site-plugin:2.0.1:site (default-site) @ module-a —
• [INFO] Unable to load parent project from a relative path: 1 problem was encountered while building the effective model
• [FATAL] Non-readable POM C:\svn\maven-test-proj\pom.xml: C:\svn\maven-test-proj\pom.xml (The system cannot find the file specified) @ C:\svn\maven-test-proj\pom.xml for project at C:\svn\maven-test-proj\pom.xml

I'm attaching a test project which demostrates this - need to first run "mvn install" on the parent-pom project and then "mvn site" on the module-a project to see the above output

Also attaching a patch which catches FileNotFoundException and outputs a [WARNING] message instead of [FATAL] - not sure if this is the best solution, but in this circumstance its much better than seeing [FATAL} - even if the build doesn't fail.

[1] http://svn.apache.org/repos/asf/commons/proper/commons-parent/
[2] http://svn.apache.org/repos/asf/commons/proper/