Release documentation updated: https://cwiki.apache.org/confluence/display/empiredb/Release+Process
Added http://mojo.codehaus.org/animal-sniffer-maven-plugin/ to our build to make sure we stick to JDK5 api except for the jsf2 extension Cheers, Francis On 25 July 2012 09:20, Francis De Brabandere <[email protected]> wrote: > On 25 July 2012 09:16, Rainer Döbele <[email protected]> wrote: >> >> As far as I remember is at least one piece of code in our JSF-extensions >> that uses a JDK6 call, but it won't even compile when the JDK5 compatibility >> option is set. >> And I don't know if we can find an easy workaround for that. >> >> On the other hand: What's wrong with switching to JDK6 now. It's mature >> enough and a long time around. >> We don't need to stick to JDK5 forever, do we? >> The core will still build and run with JDK5. > > Ok, I was just asking, I don't mind switching :-) > Will update the release notes > > F > >> >> Regards >> Rainer >> >>> from: Francis De Brabandere [mailto:[email protected]] >>> to: [email protected] >>> re: re: Can not build with jdk5 any more >>> >>> 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 >>> >
