While I read the doc, it didn't seem applicable. Now that you tell me that there's no special trickery going on that tries to force 1.4 on mojo projects, I'm off to revisit all the poms to see there's something I missed.
On Sun, Dec 20, 2009 at 8:51 PM, Barrie Treloar <baerr...@gmail.com> wrote: >> On Sun, Dec 20, 2009 at 5:26 PM, Barrie Treloar <baerr...@gmail.com> wrote: >>> On Sat, Dec 19, 2009 at 9:48 AM, Benson Margulies <bimargul...@gmail.com> >>> wrote: >>>> The eclipse plugin forces the compiler source version to 1.4 for maven >>>> plugins. I'm building a maven plugin that I want to require 1.5. Is >>>> there a way to tell the eclipse plugin to stop harassing me? >>> >>> Did you check the docs? >>> >>> http://maven.apache.org/plugins/maven-eclipse-plugin/trouble-shooting/index.html > > On Mon, Dec 21, 2009 at 9:34 AM, Benson Margulies <bimargul...@gmail.com> > wrote: >> I did. > > To my knowledge there is nothing in the eclipse plugin that forces > compiler source values. > > This, as described in the above links, is taken from the > maven-compiler-plugin. > > What do the relevant bits of your pom look like? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
