Suddenly, JabRef will not start. I get a popup saying:
To open "JabRef.app" you need a Java SE6
runtime. Would you like to install one now ? [not now][install]
Clicking on "install" starts an installation process.
Everything was fine yesterday. OSX Mavericks was installed this morning, which may be related to the problem.
JabRef 2.9.2 OSX is installed.
Java version 1.7.0_45 was reinstalled.
Other applications which require Java run fine.
Any ideas ? Other than installing Java SE6...
Thanks,
Denis
Update:
The JWS version runs, but with annoying warnings.
Building from source using Jakarta ant 1.9.2:
"ant jars" builds the JabRef.jar file which runs ok, but no JabRef.app, and the window always starts out minimised (minor issues clearly).
"ant compile unjarlib osx jars osxjar" gives the following error:
[javac] ../jabref-2.9.2/build.xml:231: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 1 source file to ../jabref-2.9.2/build/classes [javac] [javac] WARNING [javac] [javac] The -source switch defaults to 1.7 in JDK 1.7. [javac] If you specify -target 1.6 you now must also specify -source 1.6. [javac] Ant will implicitly add -source 1.6 for you. Please change your build file. [javac] warning: [options] bootstrap class path not set in conjunction with -source 1.6 [javac] ../jabref-2.9.2/src/osx/osxadapter/OSXAdapter.java:14: error: unmappable character for encoding UTF8 [javac] Copyright: � Copyright 2003 Apple Computer, Inc. All rights reserved. [javac] ^ [javac] 1 error [javac] 1 warning
BUILD FAILED
I do have a workable version of JabRef.jar, which is fine as far as I am concerned.
Last edit: Denis 2013-10-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The last build error above was fixed by removing the copyright symbol in OSXAdapter.java before running ant. The build succeeds, and I get a JabRef.app which continues to give me the same error message about Java SE6. However, the JabRef.jar file runs correctly.
Last edit: Denis 2013-10-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Suddenly, JabRef will not start. I get a popup saying:
Clicking on "install" starts an installation process.
Everything was fine yesterday. OSX Mavericks was installed this morning, which may be related to the problem.
JabRef 2.9.2 OSX is installed.
Java version 1.7.0_45 was reinstalled.
Other applications which require Java run fine.
Any ideas ? Other than installing Java SE6...
Thanks,
Denis
Update:
The JWS version runs, but with annoying warnings.
Building from source using Jakarta ant 1.9.2:
"ant jars" builds the JabRef.jar file which runs ok, but no JabRef.app, and the window always starts out minimised (minor issues clearly).
"ant compile unjarlib osx jars osxjar" gives the following error:
[javac] ../jabref-2.9.2/build.xml:231: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 1 source file to ../jabref-2.9.2/build/classes
[javac]
[javac] WARNING
[javac]
[javac] The -source switch defaults to 1.7 in JDK 1.7.
[javac] If you specify -target 1.6 you now must also specify -source 1.6.
[javac] Ant will implicitly add -source 1.6 for you. Please change your build file.
[javac] warning: [options] bootstrap class path not set in conjunction with -source 1.6
[javac] ../jabref-2.9.2/src/osx/osxadapter/OSXAdapter.java:14: error: unmappable character for encoding UTF8
[javac] Copyright: � Copyright 2003 Apple Computer, Inc. All rights reserved.
[javac] ^
[javac] 1 error
[javac] 1 warning
BUILD FAILED
I do have a workable version of JabRef.jar, which is fine as far as I am concerned.
Last edit: Denis 2013-10-26
The last build error above was fixed by removing the copyright symbol in OSXAdapter.java before running ant. The build succeeds, and I get a JabRef.app which continues to give me the same error message about Java SE6. However, the JabRef.jar file runs correctly.
Last edit: Denis 2013-10-30