> BTW, where do I put things that define ${maven.java.version}?
In properties inside the pom.
<properties>
<maven.java.version>1.5</maven.java.version>
</properties>
You could also specify them in a profile in settings.xml, but in this
particular case, that doesn't make sense (at least to me). Properties in
settings.xml should include things that are developer-specific, like the
path to some execuatble.
Justin
-----Original Message-----
From: John Wooten [mailto:[email protected]]
Sent: Monday, March 09, 2009 11:19 AM
To: Maven Users List
Subject: Re: Eclipse and maven
Thanks!
I went through removing all plugins in the reporting section and slowly
adding one at a time back, checking each time, and finally got it all
working!
Appreciate the help.
BTW, where do I put things that define ${maven.java.version}? I had to
put actual "1.5" there since it wasn't getting resolved. If in the
settings.xml, where does that go and what is the syntax?
On Mar 3, 2009, at 3:08 PM, Edelson, Justin wrote:
> This is very strange. It looks like an older version of the master is
> being used.
>
> If you run help:effective-pom against the master, does it correctly
> show targetJdk = 1.5?
>
> You should probably get rid of the duplicate plugin configuration
> within the reporting section. I don't see how that could cause this
> problem, but it may be related.
>
> Justin
>
>
> -----Original Message-----
> From: John Wooten [mailto:[email protected]]
> Sent: Tuesday, March 03, 2009 1:59 PM
> To: Maven Users List
> Subject: Re: Eclipse and maven
>
> Here is the link to the info you requested. Thanks a lot for taking
> the time to help with this.
>
> http://pastebin.com/m57fb8d1e
>
>
> On Mar 2, 2009, at 4:25 PM, Edelson, Justin wrote:
>
>> John-
>> Sorry I didn't get back to you about your 1.5 problem over the
>> weekend. Can you post your pom and the output of mvn
>> help:effective-pom to a pastebin and send the link?
>>
>> As for the rest of it, I don't understand what you are trying to
>> accomplish. commons, log4j, etc. are already in the central
>> repository. If you need to share 3rd party JARs, use a repository
>> manager (Archiva, Nexus, etc.).
>>
>> Justin
>>
>> ________________________________
>>
>> From: John Wooten [mailto:[email protected]]
>> Sent: Mon 3/2/2009 4:13 PM
>> To: Maven Users List
>> Subject: Re: Eclipse and maven
>>
>>
>>
>> I haven't fixed the problem with java 1.5 yet, but am moving all my
>> projects into the maven convention. Now, I have the question:
>>
>> In my eclipse projects, I have a separate project called "libs" where
>> I have been putting all of my external jars like java-commons, log4j,
>> etc. Then in the classpath I add that project, and select the jars I
>> need. I'd like to move to using the maven repository inside the
>> eclipse projects and get rid of the "libs" project. How do I do that
>> so that others who check out the eclipse projects still have access
>> to
>
>> the necessary jars? Do they have to install maven also? What is the
>> best direction here?
>>
>> On Feb 28, 2009, at 12:55 PM, Edelson, Justin wrote:
>>
>>> 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]
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> 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]
