What about to set the compile / source level to jdk 6? http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html
As long as we don't use jdbc or other integrations it should be fine. It's only a suggestion. kind regards Tobias P.S.: I think most Wicket 6 users are already using jdk > 7. > Am 09.06.2015 um 15:24 schrieb Martijn Dashorst <martijn.dasho...@gmail.com>: > > All, > > I'm currently trying to build a release with Maven but ran into a snag > that Maven 3.3 doesn't support running on java 6 anymore. However I > like to ensure our wicket 6.x releases are built with an actual Java 6 > release, so I am in the process of using toolchains [1] for the > release building. > > Maven toolchains allow you to specify a required Java version in your > pom, and in your local maven settings (~/.m2/toolchains.xml) where > Maven can find the particular JDK version. > > This allows us to run Maven with Java 7 and compile using an actual Java 6 > JDK. > > Martijn
