Maven 2.x PMD Plugin

Wrong resolving ruleset resource for multi module project

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 2.4
  • Fix Version/s: 2.5
  • Component/s: PMD
  • Labels:
    None
  • Environment:
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

In our company using in multi module project pmd ruleset, where on each module is used others rules of ruleset.
Real case on project:

parent
  |- module-1 (depends on module-3)
  |- module-2 (depends on module-1)
  \- module-3

Order of running in reactor is: module-3, module-1, module-2.
If set of rules in module-1 is included in module-1, etc., problem can not turn up.
But ex. module-1 set defines rule, which is not included in module-2 and we violate this rule, pmd plugin fails.
Behavior is that component org.codehaus.plexus.resource.ResourceManager is instantiated as singleton.

I found workaround for this issue, using newer version of plexus-resources dependency, where instantiation-strategy is changed to per-lookup.

<plugin>
  <artifactId>maven-pmd-plugin</artifactId>
  <dependencies>
    <dependency>
      <groupId>org.codehaus.plexus</groupId>
      <artifactId>plexus-resources</artifactId>
      <version>1.0-alpha-5</version>
    </dependency>
  </dependencies>
</plugin>

I attach test-case (as IT test)

Issue Links

Activity

Hide
Herve Boutemy added a comment -

done in MPMD-120, for other bugs in plexus-resources 1.0-alpha-4

Show
Herve Boutemy added a comment - done in MPMD-120, for other bugs in plexus-resources 1.0-alpha-4

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: