title: Maven plugin dependency cannot use parent pom property
body: <p>I'm hitting a weird edge use case with Maven &amp; curious why it's behaving the way it does. </p>
  
  <p>I'm defining a property in my parent project like so:</p>
  
  <pre><code>  &lt;properties&gt;
        &lt;some.property.version&gt;1.0.0.0&lt;/some.property.version&gt;
    &lt;/properties&gt;
  </code></pre>
  
  <p>Now, in a module, I set a version of a dependency for a plugin like so:</p>
  
  <pre><code>  &lt;build&gt;
        &lt;plugins&gt;
            &lt;plugin&gt;
                &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
                &lt;artifactId&gt;bob&lt;/artifactId&gt;
                &lt;version&gt;1.0.0.0&lt;/version&gt;
                &lt;dependencies&gt;
                    &lt;dependency&gt;
                        &lt;groupId&gt;org.example&lt;/groupId&gt;
                        &lt;artifactId&gt;example&lt;/artifactId&gt;
                        &lt;version&gt;${some.property.version}&lt;/artifactId&gt;
                    &lt;/dependency&gt;
                &lt;/dependencies&gt;
            &lt;/plugin&gt;
        &lt;/plugins&gt;
    &lt;/build&gt;
  </code></pre>
  
  <p>This causes Maven to spit out an error:</p>
  
  <p>[ERROR]     'build.plugins.plugin[org.apache.maven.plugins:bob].dependencies.dependency.version' for org.example:example:jar must be a valid version but is '${some.property.version}'. @ line 350, column 16</p>
  
  <p>What's bizarre to me is if I move the property being defined down into the module itself, Maven compiles just fine. Is this a bug? Or are there restrictions of visibility to parent pom properties in a plugin for a module?</p>