On Apr 11, 2010, at 2:02 AM, nicolas de loof wrote: > Will this change be supported in m2eclipse ? I mean : will m2e detect the > maven-compiler-plugin 2.3+ version and set JRE1.5 classpath container ? >
Configurators operate on the effective POM. So when we update M2Eclipse to use 3.0-beta-1 where the maven-compiler-plugin version 2.3 will be injected into the model then yes. > 2010/4/10 Stephen Connolly <stephen.alan.conno...@gmail.com> > >> +1 >> >> Sent from my [rhymes with tryPod] ;-) >> >> On 10 Apr 2010, at 12:40, Jason van Zyl <ja...@sonatype.com> wrote: >> >> Hi, >>> >>> This was simply to bump the default source/target to 1.5. I don't want >>> 3.0-beta-1 released requiring people to set these as they should be defaults >>> now. >>> >>> Staging repo: >>> https://repository.apache.org/content/repositories/maven-011 >>> >>> All we fixed was this: >>> http://jira.codehaus.org/browse/MCOMPILER-80 >>> >>> Guide to testing staged releases: >>> http://maven.apache.org/guides/development/guide-testing-releases.html >>> >>> Vote open for 72 hours. >>> >>> [ ] +1 >>> [ ] +0 >>> [ ] -1 >>> >>> +1 from me. >>> >>> Thanks, >>> >>> Jason >>> >>> ---------------------------------------------------------- >>> Jason van Zyl >>> Founder, Apache Maven >>> http://twitter.com/jvanzyl >>> ---------------------------------------------------------- >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl ----------------------------------------------------------
