[MNG-3941] Execution project is accessible to later mojo executions

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.9, 2.1.0-M1
• Fix Version/s: 3.0-alpha-3
• Component/s: Plugins and Lifecycle
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 25/Dec/08 05:56
• Updated: 06/Apr/15 01:14
• Resolved: 30/Jul/09 12:09

Description

As MSHADE-44 shows, the execution project created for a mojo execution that forks the lifecycle is still accessible to later mojo executions althought these later mojo executions did not request a forked lifecycle. While mojos should not depend on the execution project unless they fork by themselves, the core should probably wipe out any mojo-related state bits from the MavenProject instance before executing another mojo.

IIRC, the same applies to the project dependencies available to a mojo. Currently, badly written mojos can still get proper dependency sets if some other mojo triggered dependency resolution before. For deterministic behavior, mojos should only see those deps that they requested themselves via {@requiresDependencyResolution.

Issue Links

• is related to: MNG-3297 maven should not give dependencies to plugins that don't @requireDependencyResolution
• is related to: MSHADE-44 Attaching classified artifacts not working properly