Hi, Jörn, Do you know how to ensure that the java compatibility level? The note at the bottom of http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html<http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html:>says that setting source/target is not enough, but I can't understand what they mean with configure the compiler's boot classpath to match the target JRE. Do we have to hard code the classpath?
Thanks William On Wed, Dec 15, 2010 at 10:10 AM, Jörn Kottmann <[email protected]> wrote: > On 12/15/10 1:03 PM, [email protected] wrote: > >> Hi, >> >> When I try to load the project from Eclipse, some build errors appear >> because the project is set to use Java 1.5, but the code use Java 1.6 API >> String.isEmpty for example. >> >> It is OK to build using command line, but using M2Eclipse it fails to >> build. >> >> Maybe I'm missing something. >> >> By the way, isn't it better to keep Java 1.5 compatibility? >> > > Yes, that is a little embarrassing, it should have been found > while making the 1.5.0 release. I think we should fix it now > and ensure that the java compatibility level is enforced during > our release process. > > Can you open a jira for it and fix the code ? > > Thanks, > Jörn >
