[
http://jira.codehaus.org/browse/MPMD-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MPMD-110.
------------------------------
Resolution: Fixed
Fix Version/s: 2.5
Assignee: Herve Boutemy
done in MPMD-120, for other bugs in plexus-resources 1.0-alpha-4
> Wrong resolving ruleset resource for multi module project
> ---------------------------------------------------------
>
> Key: MPMD-110
> URL: http://jira.codehaus.org/browse/MPMD-110
> Project: Maven 2.x PMD Plugin
> Issue Type: Bug
> Components: PMD
> Affects Versions: 2.4
> Environment: * 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"
> Reporter: Petr Prochazka
> Assignee: Herve Boutemy
> Priority: Blocker
> Fix For: 2.5
>
> Attachments: multi-module-with-different-ruleset.zip
>
>
> In our company using in multi module project pmd ruleset, where on each
> module is used others rules of ruleset.
> Real case on project:
> {code}
> parent
> |- module-1 (depends on module-3)
> |- module-2 (depends on module-1)
> \- module-3
> {code}
> 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*.
> {code:xml}
> <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>
> {code}
> I attach test-case (as IT test)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
