Maven 2.x PMD Plugin

Having an equivalent for auxclasspath option

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.4
  • Fix Version/s: 3.0
  • Component/s: PMD
  • Labels:
    None
  • Environment:
    PMD 4.2.3
  • Number of attachments :
    1

Description

Hi,

PMD 4.2.3 introduced the option "auxclasspath" described as follows in the PMD help :
"-auxclasspath: specifies the classpath for libraries used by the source code (used by type resolution)"

Currently, there seems to be no way to use this very useful option in the PMD maven2 plugin.
I either found no workaround to deal with type resolution inside the project that has just been built through the compile maven goal.

This would be great !

Benjamin

  1. Text File
    MPMD-89.patch
    26/Jan/13 6:55 AM
    13 kB
    Benjamin Bentmann

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Herve Boutemy added a comment -

can you provide an unit test, showing a different result when this option is used and when it is not used?

Show
Herve Boutemy added a comment - can you provide an unit test, showing a different result when this option is used and when it is not used?
Hide
Permalink
Colin Alworth added a comment -

I don't yet have a unit test, but the use case is that you want PMD to analyze the classes themselves in addition to the AST. Type resolution uses the auxclasspath parameter to make not just the source but the classes available on the JVM.

My use case is that we have specific rules about how a class may be used, and we are trying to enforce these by way of a rule. Every subclass of a given class may provide several methods which may be called via reflection remotely. The goal of this tests is to statically ensure that only legal methods are called.

Another example of how this can be helpful is the built in abstract junit rule (http://pmd.sourceforge.net/xref/net/sourceforge/pmd/rules/junit/AbstractJUnitRule.html). This checks, (among other things) whether the test is written to junit version 3 or 4, and allows subclasses to ask if a given method is a test method. This is not possible for JUnit 3 tests classes if the test class cannot be inspected to see if it extends TestCase.

Show
Colin Alworth added a comment - I don't yet have a unit test, but the use case is that you want PMD to analyze the classes themselves in addition to the AST. Type resolution uses the auxclasspath parameter to make not just the source but the classes available on the JVM. My use case is that we have specific rules about how a class may be used, and we are trying to enforce these by way of a rule. Every subclass of a given class may provide several methods which may be called via reflection remotely. The goal of this tests is to statically ensure that only legal methods are called. Another example of how this can be helpful is the built in abstract junit rule ( http://pmd.sourceforge.net/xref/net/sourceforge/pmd/rules/junit/AbstractJUnitRule.html ). This checks, (among other things) whether the test is written to junit version 3 or 4, and allows subclasses to ask if a given method is a test method. This is not possible for JUnit 3 tests classes if the test class cannot be inspected to see if it extends TestCase.
Hide
Permalink
Benjamin Bentmann added a comment -

That might do.

Show
Benjamin Bentmann added a comment - That might do.
Hide
Permalink
Olivier Lamy added a comment -

sounds good.
Feel free to apply it yourself

Show
Olivier Lamy added a comment - sounds good. Feel free to apply it yourself
Hide
Permalink
Benjamin Bentmann added a comment -

Added typeResolution parameter in r1439834.

Show
Benjamin Bentmann added a comment - Added typeResolution parameter in r1439834 .

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Benjamin Pochat
Vote (1)
Watch (5)

Dates

  • Created:
    Updated:
    Resolved: