Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 345510

Summary:	Using methods available in Java 6 only does not cause compile error
Product:	[RT] Jetty	Reporter:	Michael Gorovoy <mgorovoy>
Component:	build	Assignee:	Jesse McConnell <jesse.mcconnell>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	janb, jetty-inbox, mgorovoy
Version:	7.4.0
Target Milestone:	7.4.x
Hardware:	PC
OS:	Linux
Whiteboard:

Description Michael Gorovoy

2011-05-11 20:49:54 EDT

I've been able to use String.isEmpty() method in my code, and neither Eclipse, nor Maven cli compile had given me a compile error.

Comment 1 Jan Bartel

2011-06-30 00:24:54 EDT

I'm changing this to an enhancement, as perhaps there is something that can be done with maven-toolchain to set the jdk ... although we don't want to have to set toolchain.xml files in everyone's .m2 dir in order to do a compile ...

Comment 2 Jesse McConnell

2011-07-19 15:19:00 EDT

properly configured eclipse this is not a big deal and I ran across this the other day with a commit of gregs and eclipse had flagged it automatically for me...

so I don't think its worth spending any time, as a developer just make sure your toolchain is setup correctly

if this becomes a systemic issue that starts chewing up more time then the odd committ here and there then I'll reopen and investigate further

Comment 3 Michael Gorovoy

2011-07-19 16:47:43 EDT

I agree that this is not a big deal. I suspect this might have been caused by an older version of m2eclipse not importing the compiler compliance settings correctly. I've re-imported the projects into my workspace following the move to Git and this time it got set up properly.

-Michael