[MNG-4269] [regression] Invocation of just installed plugin on its plugin project can fail with ComponentLookupException for mojo class

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-3
• Fix Version/s: 3.0-alpha-3
• Component/s: Artifacts and Repositories, Plugins and Lifecycle
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 31/Jul/09 12:20
• Updated: 31/Jul/09 13:12
• Resolved: 31/Jul/09 13:12

Description

This is a side effect of my initial solution for MNG-3043: Basically, reactor resolution is too eager and resolves artifacts from project output even if the project has not been build in the current reactor build. In other words, a possibly cleaned (but not deleted) output directory is used for the artifact instead of the file from the repo.

For instance, the following steps on a simple plugin project will fail

• mvn install to install the plugin JAR locally
• erasing the contents of the project's target/classes directory, but leaving the directory itself existent
• mvn the-just-installed-plugin:goal
  The last invocation will resolve the plugin from its own invalidate output directory.

Issue Links

• is related to: MNG-3043 Allow 'mvn test' to work with test-jar dependencies in a reactor