There's a difference in building with and building for. A jdk6 empire-db buid built for java 5 runtime can contain java 6 api calls that will fail at runtime. As far as I know there is no way to use 2 sdks to do a single maven build... There are however plugins that can check for these issues but still a user would need jdk6 to build our project. Does jsf2 really need jdk6?
F On Jul 24, 2012 9:03 PM, "Rainer Döbele" <[email protected]> wrote: > I am not sure about your question. > We're only building the JSF classes with JDK6, and the rest with JDK5. > > Can't we keep it like this? > > Regards > Rainer > > > > from: Francis De Brabandere [mailto:[email protected]] > > to: [email protected] > > re: Can not build with jdk5 any more > > > > The JSF extension needs jdk6. > > > > Should we drop jdk5 building/support? I normally build all releases > > with jdk5 to be sure there are no jdk6-7 api calls. > > > > <properties> > > <maven.compile.source>1.6</maven.compile.source> > > <maven.compile.target>1.6</maven.compile.target> > > </properties> > > > > INFO] Compiling 42 source files to > > /home/francisdb/workspace/empire-db-parent/empire-db- > > jsf2/target/classes > > [INFO] ------------------------------------------------------------- > > [ERROR] COMPILATION ERROR : > > [INFO] ------------------------------------------------------------- > > [ERROR] Failure executing javac, but could not parse the error: > > javac: invalid flag: -s > > > > F >
