If the 1.6 JVM tries to load a class that was compiled with 1.7, one would to expect to have an java.lang.ClassFormatError exception to be thrown. Most likely this will be a java.lang.UnsupportedClassVersionError [http://docs.oracle.com/javase/7/docs/api/java/lang/UnsupportedClassVersionError.html].
On the other hand it should be possible to run a class (jar) compiled with 1.6 on a 1.7 JVM. -----Original Message----- From: Jörn Kottmann [mailto:kottm...@gmail.com] Sent: Wednesday, October 30, 2013 3:40 AM To: dev@opennlp.apache.org Subject: Re: Move to Java 7 I know you are working on an OpenNLP contrib to Lucene, would this be affected through the update? Jörn On 10/30/2013 08:36 AM, Jörn Kottmann wrote: > Hi Lance, > > please share you concerns with us. OpenNLP 1.6.0 will require a Java 7 > VM, if other parts of your project only require Java 6 this will all > work together on a Java 7 VM. > > Do you have a production system where you can only run java 6 VMs? > > At which time do you plan to update to java 7? It will probably take > us a few month until OpenNLP 1.6.0 is out. > > Jörn > > On 10/29/2013 11:02 PM, Lance Norskog wrote: >> Will this screw up a project that uses OpenNLP jar if the project is >> still on Java 6? >> >> Lance >> >> On 10/29/2013 03:29 AM, Mark G wrote: >>> Ok, thanks! I didn't know which server was the build server... same >>> as SVN? >>> I will try to commit some java 7 code now MG >>> >>> >>> On Tue, Oct 29, 2013 at 6:25 AM, Jörn Kottmann <kottm...@gmail.com> >>> wrote: >>> >>>> On 10/29/2013 11:11 AM, Mark G wrote: >>>> >>>>> OK, I committed the POM only just to see if the CI server has Java >>>>> 7 in >>>>> it's path. Since we haven't gotten a build error yet, it may be fine. >>>>> Haven't tried committing any code with J7 objects. >>>>> >>>> I updated the configuration on the build server is now to Java 7, >>>> to do >>>> this you have to log >>>> in there with your apache id and then go to "Configuration" of the >>>> OpenNLP >>>> project. >>>> >>>> Jörn >>>> >> >
