From 9e14537be510f8a57c22ea761ee7c1528d0ea486 Mon Sep 17 00:00:00 2001 From: Ben Soares Date: Tue, 18 Aug 2020 08:40:33 +0100 Subject: [PATCH] JAL-3676 Start of documentation in help pages logging.html --- help/help/html/logging.html | 66 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 help/help/html/logging.html diff --git a/help/help/html/logging.html b/help/help/html/logging.html new file mode 100644 index 0000000..2993370 --- /dev/null +++ b/help/help/html/logging.html @@ -0,0 +1,66 @@ + + + +Logging and Reporting Bugs + + +

+
+ Logging and Reporting Bugs +
+

+ +

Logging

+

+ Jalview creates logs that can be extremely useful for diagnosing, or help to provide a workaround for, specific problems that you might encounter. +

+

+ The primary place to look for logs is in the Java Console which you can open from within Jalview by going to the Tools menu and checking the box next to Show Java Console. This option is stored in your Jalview preferences file and so is remembered across Jalview sessions. +

+

+ The Java Console will show you information about what the Jalview application is doing (often in the background) whilst it is running. +

+

+ However, it is possible that some early logging information from when Jalview is initially launched, is not shown in the Java Console: +
+ If you are using a version of Jalview installed from one of our install4j installers, then Jalview's initial launch logging can be found in + 

JALVIEW_APP_DIR/launcher.log
+ where JALVIEW_APP_DIR is the directory that Jalview's application was installed into. +
+ For Jalview 2.11.0 onwards: + +
+ Whereas if you are using the Jalview executable jar file (also used by bioconda installations) then a minimised launcher will output logging information to STDOUT and STDERR. +

+ +

Java Console and Log Level

+ + +

Reporting Bugs

+ + + + -- 1.7.10.2