Yes... a corporate or some other higher level pom is typically how you configure this across lots of projects. But even if you dont ... its two lines of config on the compiler plugin.
Manfred Sander Verhagen wrote on 17.06.2015 15:16: > I wonder if this would be a good candidate for a corporate POM that deals with > this kind of configuration? > > > > Sander Verhagen > [ san...@sanderverhagen.net ] > > NOTICE: my e-mail address has changed. You may still e-mail me at > verha...@sander.com but you will see me using san...@sanderverhagen.net from > now on. Feel free to update your address book. > >> -----Original Message----- >> From: Mangold, Kevin C. [mailto:kevin.mang...@nist.gov] >> Sent: Wednesday, June 17, 2015 12:55 >> To: dev@maven.apache.org >> Subject: Default Maven Compiler Version >> >> Why does the maven compiler plugin STILL target 1.5 by default and not the >> JDK's current version? This seems completely backwards. We use CI tools to >> test against different JDK versions and architectures and it is a massive >> pain >> to implement all these workarounds to have the compiler target each JDK's >> respective version. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
