Dependency on pom-project not resolved in reactor on multi-module build

I'm running into the issue described in the following thread:

http://maven.40175.n5.nabble.com/Dependency-on-pom-project-not-resolved-in-reactor-on-multi-module-build-td3309198.html

I can't find a similar bug report, so I'm guessing one was never submitted. The original poster included a sample project. I'll attach it here. To reproduce the issue, run 'mvn package' on the attached project. I would expect the POM dependency for module A to get resolved as part of the reactor, but it does not.

This can cause unexpected behavior for any multi-module projects that rely on dependency grouping modules as described here:

http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-pom-best-practice.html

Rather than getting dependency information from the current reactor, a stale POM from the local (or remote) repository is used. If no POM has ever been installed, the build fails instead.