You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just installed JabRef 3.2 on Windows 7 (java version "1.8.0_73", 32 bit) and checked the error console to see if it showed why an external fetcher was failing (see #818). However there was nothing logged in error console at all.
Therefore I went ahead and tried a development snapshot (JabRef_windows_3_3dev--snapshot--2016-02-12--master--c917a4a.exe) since I noticed #484 added a --debug command line switch.
However the error console is still empty (I tried running JabRef.exe --debug as well as java -jar JabRef-3.3dev-[...].jar --debug)
The only change is that the latter produces a whole lot of output on the commandline which seems to be broken though:
Might be a duplicate of #743 (at least the latter part). In that case feel free to close.
It doesn't explain why the error console stays empty though (given a failing full text fetcher is supposed to log something to error console to start with).
I just installed JabRef 3.2 on Windows 7 (java version "1.8.0_73", 32 bit) and checked the error console to see if it showed why an external fetcher was failing (see #818). However there was nothing logged in error console at all.
Therefore I went ahead and tried a development snapshot (JabRef_windows_3_3dev--snapshot--2016-02-12--master--c917a4a.exe) since I noticed #484 added a
--debug
command line switch.However the error console is still empty (I tried running
JabRef.exe --debug
as well asjava -jar JabRef-3.3dev-[...].jar --debug
)The only change is that the latter produces a whole lot of output on the commandline which seems to be broken though:
The text was updated successfully, but these errors were encountered: