Using a specific plugin version in custom lifecycle

[Sebastian Annies]

Hi, 

we are using a custom lifecycle and bind the maven-source-plugin in
version 2.1 to the verify phase. In the 2.X branch it always worked
perfectly. But now I tried alpha-3 and 4 and it seems that Maven uses
the maven-source-plugin in version 2.0.4 even though I explicitly
require 2.1 ( 2.0.4 does not provide the "jar-no-fork" goal and the
build breaks)!
Has anyone of you experienced similar behavior or is intended to work
that way? 

Best Regards,
Sebastian

Have a look at my DefaultLifecycleMapping: 

  <lifecycle>
   <id>default</id>
   <phases>
    
<generate-sources>net.jangaroo:ext-xml-maven-plugin:${pom.version}:extxml</generate-sources>
    
<process-resources>org.apache.maven.plugins:maven-resources-plugin:resources</process-resources>
    <compile>net.jangaroo:jangaroo-maven-plugin:${pom.version}:compile</compile>
    
<generate-test-resources>net.jangaroo:jangaroo-maven-plugin:${pom.version}:unpack-jangaroo-test-dependencies</generate-test-resources>
    
<process-test-resources>org.apache.maven.plugins:maven-resources-plugin:testResources</process-test-resources>
    
<test-compile>net.jangaroo:jangaroo-maven-plugin:${pom.version}:testCompile</test-compile>
    <test>net.jangaroo:jangaroo-maven-plugin:${pom.version}:test</test>
    <package>net.jangaroo:jangaroo-maven-plugin:${pom.version}:package</package>
    
<verify>org.apache.maven.plugins:maven-source-plugin:2.1:jar-no-fork</verify>
    <install>org.apache.maven.plugins:maven-install-plugin:install</install>
    <deploy>org.apache.maven.plugins:maven-deploy-plugin:deploy</deploy>
   </phases>
  </lifecycle>
 <lifecycle>