Maven 2 & 3

remove plugin listeners for minor memory improvement and to avoid scanning descriptors from dependencies of plugins

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.1.0-M1
  • Fix Version/s: 2.1.0
  • Component/s: Plugins and Lifecycle
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

currently, the plugin collector and plugin validator are run for each dependency of the plugin at a later stage. while this has no known negative side effects other than performance and memory consumption, the behaviour is incorrect as it is only intended to discover the mojos in the main plugin.

Activity

Hide
Permalink
Brett Porter added a comment -

I have tested this with existing ITs including those for MNG-4091 and a plugin that uses the maven-inherit-plugin from pax construct (http://www.ops4j.org/projects/pax/construct/maven-inherit-plugin/index.html)

Show
Brett Porter added a comment - I have tested this with existing ITs including those for MNG-4091 and a plugin that uses the maven-inherit-plugin from pax construct (http://www.ops4j.org/projects/pax/construct/maven-inherit-plugin/index.html)

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.