notice that there is another case to take care: if you use dependencies compiled in Java 6 (like guava, for example)
the solution for this additional case is http://mojo.codehaus.org/extra-enforcer-rules/enforceBytecodeVersion.html Regards, Hervé Le vendredi 24 mai 2013 19:44:10 Hervé BOUTEMY a écrit : > http://mojo.codehaus.org/animal-sniffer-maven-plugin/ > > Le vendredi 24 mai 2013 13:29:03 Russell Gold a écrit : > > By default, as I understand it, Maven 3 compiles with the source and > > target > > options set to 1.5. This guarantees that later language features (such as > > diamond notation) will result in compile errors, and the generated classes > > will run in a JDK 1.5 JVM. But what about API calls? Does the compile > > plugin have a way to ensure that references to APIs created in later > > versions of the JDK will fail? > > > > I've seen a trick that uses the JDK 1.5 bootclasspath to do this; does > > Maven have a cleaner solution? > > > > Thanks, > > Russ > > ----------------- > > Come read my webnovel, Take a Lemon <http://www.takealemon.com>, > > and listen to the Misfile radio play > > <http://www.gold-family.us/audio/misfile.html>! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
