source and target are not valid configuration parameters for pmd. The parameter
is called targetJdk.
The way I deal with this problem is to have a property called
maven.java.version and then reference that wherever necessary. Currently in our
organizational pom, these are:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>${maven.java.version}</source>
<target>${maven.java.version}</target>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>${plugin.version.javadoc}</version>
<configuration>
<source>${maven.java.version}</source>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
<version>${plugin.version.pmd}</version>
<configuration>
<targetJdk>${maven.java.version}</targetJdk>
</configuration>
</plugin>
AFAIK, there is no JDK version parameter for checkstyle or jdepend.
Hope this helps...
Justin
________________________________
From: John Wooten [mailto:[email protected]]
Sent: Sat 2/28/2009 12:40 PM
To: Maven Users List
Subject: Re: Eclipse and maven
I have the following in a terminal window:
[woo] 543 > javac -version
javac 1.5.0_16
Now, I have the java version in each of the plugins as 1.5
viz:
jdepend plugin, surefire plugin, pmd plugin, and checkstyle plugin. I
didn't see where to specify that for the javadoc.
Still get:
[INFO] Generating "PMD Report" report.
[WARNING] Unable to locate Source XRef to link to - DISABLED
[WARNING] File encoding has not been set, using platform encoding
MacRoman, i.e. build is platform dependent!
[WARNING] Error while parsing /Users/woo/Development/workspaces/areteq/
modules/Foundation/src/main/java/com/areteq/common/
HashMapHandler.java: Can't use generics unless running in JDK 1.5 mode!
[WARNING] Error while parsing /Users/woo/Development/workspaces/areteq/
modules/Foundation/src/main/java/com/areteq/common/
HashMapHandler.java: Can't use generics unless running in JDK 1.5 mode!
In the <reports> section I have
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
<configuration>
<source>1.5</source>
<target>1.5</target>
<rulesets>
<ruleset>/rulesets/basic.xml</ruleset>
<ruleset>/rulesets/imports.xml</ruleset>
<ruleset>/rulesets/unusedcode.xml</ruleset>
<ruleset>/rulesets/finalizers.xml</ruleset>
</rulesets>
</configuration>
</plugin>
On Feb 27, 2009, at 7:25 PM, Edelson, Justin wrote:
> I believe that's a javadoc warning (not error). In addition to maven-
> compiler-plugin, you also need to specify the Java version in the
> javadoc plugin (in the reporting section) and, if you use it, the
> pmd plugin.
>
> Justin
>
> ________________________________
>
> From: John Wooten [mailto:[email protected]]
> Sent: Fri 2/27/2009 7:16 PM
> To: Maven Users List
> Subject: Re: Eclipse and maven
>
>
>
> That is 1 place I have it. Still get error.
>
> Pardon bad thumbsmanship. Sent from mobile phone.
>
> On Feb 27, 2009, at 7:05 PM, Rusty Wright <[email protected]>
> wrote:
>
>> Only one plugin needs that:
>>
>> <plugins>
>> <plugin>
>> <artifactId>maven-compiler-plugin</artifactId>
>>
>> <configuration>
>> <source>1.5</source>
>> <target>1.5</target>
>> </configuration>
>> </plugin>
>> etc.
>>
>>
>> John Wooten wrote:
>>> I have added:
>>> <configuration>
>>> <source>1.5</source>
>>> <target>1.5</target>
>>> </configuration>
>>> to each plugin and I still get:
>>> [WARNING] Error while parsing /Users/woo/Development/workspaces/
>>> areteq/modules/Foundation/src/main/java/com/areteq/common/
>>> HashMapHandler.java: Can't use generics unless running in JDK 1.5
>>> mode!
>>> Would be nice to specify this in one place ( run in JDK 1.5 mode ).
>>> On Feb 27, 2009, at 4:06 PM, Eugene Kuleshov wrote:
>>>>
>>>>
>>>> See comparison at
>>>> http://docs.codehaus.org/display/MAVENUSER/Eclipse+Integration
>>>>
>>>> regards,
>>>> Eugene
>>>>
>>>>
>>>>
>>>> supareno wrote:
>>>>>
>>>>> David,
>>>>>
>>>>> http://code.google.com/p/q4e is a very good tool too
>>>>>
>>>>>> though...i would also encourage you to check out the M2Eclipse
>>>>>> plugin
>>>>>> for Eclipse. it does a really good job of helping with the
>>>>>> integration of Maven and Eclipse
>>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/Eclipse-and-maven-tp22245841p22254461.html
>>>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>> ---
>>>> ------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
