It's not a big problem but since we have to build with jdk6 we are more likely going to introduce jdk6 api in empire-db core without noticing.
I'll switch the remaining jenkins builds to jdk6 Sent with my smartphone. On Apr 15, 2012 11:27 PM, "Rainer Döbele" <[email protected]> wrote: > I was wondering why I got this compilation error from Jenkins. > From the message I could not figure out, where the problem is. > > Yes in fact (and unfortunately) there is currently one call that makes > Java 1.6 necessary (ResourceBundle.containsKey()). I might be able to find > a workaround for this, but then why should we? > For his particular module I think we can raise the requirement to Java 1.6 > since it's old and mature enough now. > Or do you think this is a problem? > > Since Jenknis now reports it is back to normal I assume, that you switched > to Java 6 for the build. > Correct? > > Rainer > > > > from: [email protected] [mailto:[email protected]] Im Auftrag von > Francis De Brabandere > > to: dev > > re: Fwd: Jenkins build is back to normal : Empire-db snapshot #421 > > > > Rainer, > > > > I see the JSF module is not JDK-5 compatible, making JDK6 mandatory to > > build empire-db. > > > > <properties> > > <maven.compile.source>1.6</maven.compile.source> > > <maven.compile.target>1.6</maven.compile.target> > > </properties> > > > > Do we really need this 1.6 target & source? We should at least > > communicate this to our users on the next release. > > > > Cheers, > > F > > > > ---------- Forwarded message ---------- > > From: Apache Jenkins Server <[email protected]> > > Date: 15 April 2012 17:47 > > Subject: Jenkins build is back to normal : Empire-db snapshot #421 > > To: [email protected], [email protected] > > > > > > See <https://builds.apache.org/job/Empire-db%20snapshot/421/> >
