Okay, I just implemented a new main class (called JabRefMain), which checks for Java 1.5 and prints warnings if a wrong JRE is found. It still tries to start JabRef nevertheless, just in case afterwards. I also modified the build-file that this new Main file is compiled using Java 1.4 and not 1.5, so we cannot use generics and such in it.
I also put in a warning for classpath/gcj virtual machines, as these have generated a couple of warnings as well. Unfortunately I don't have a Java 1.4 or classpath on my machine, so I cannot really test if it really catches all problems. I would appreciate it, if somebody could run it from the jar and see whether the warnings show up correctly (no internationalization, yet). Thanks, Christopher On Sun, 09 Sep 2007 15:25:02 +0200, Morten Omholt Alver <[EMAIL PROTECTED]> wrote: >> in the last weeks it is often asked, which is the minimum requirement >> on the >> Java Runtime Environment to run the current version of JabRef. We >> recommend >> Sun JRE version 1.5, right? > > The current version of JabRef is 2.2, and it requires Java 1.4.2. The > current beta version requires version 1.5, but I would rather > recommend 1.6. Our biggest problem is perhaps that users download 2.3 > beta without realizing that it is a beta version. > > On the other hand, I guess it wouldn't hurt to change the web site to > say 1.5 instead of 1.4.2, since the older versions run at least as > well on the newer versions. > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Jabref-devel mailing list Jabref-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jabref-devel
