Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 2.4
-
Fix Version/s: 2.5
-
Component/s: PMD
-
Labels:None
-
Environment:Hide* Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
* Java version: 1.6.0_16
* Java home: D:\java\jdk\jre
* Default locale: cs_CZ, platform encoding: Cp1250
* OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"Show* Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) * Java version: 1.6.0_16 * Java home: D:\java\jdk\jre * Default locale: cs_CZ, platform encoding: Cp1250 * OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
-
Testcase included:yes
-
Number of attachments :
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)
Attachments
Issue Links
| This issue relates to: | ||||
| MPMD-120 | Ruleset XML files containing non-ascii characters are corrupted when copied into target directory |
|
|
|
done in
MPMD-120, for other bugs in plexus-resources 1.0-alpha-4MPMD-120, for other bugs in plexus-resources 1.0-alpha-4