GP-2936: Fixed an issue that prevented the default script log file from

getting used in the user's.ghidra directory
This commit is contained in:
Ryan Kurtz
2023-02-08 10:51:42 -05:00
parent 1de4b32e51
commit 8da5b1593c
3 changed files with 7 additions and 7 deletions

View File

@@ -151,6 +151,7 @@ public class Application {
/**
* If the Application was previously initialized with logging disabled, this method
* may be used to perform delayed logging initialization.
*
* @param logFile application log file, if null the default <i>application.log</i> will be stored
* within the user's application settings directory
* @param scriptLogFile scripting log file, if null the default <i>script.log</i> will be stored
@@ -169,10 +170,7 @@ public class Application {
logFile = new File(app.layout.getUserSettingsDir(), "application.log");
}
if (scriptLogFile == null) {
// Some clients pass null for the script file, as they do not support scripting. In
// that case, just have the system use the application log as the script log. This
// prevents the logging system from creating an oddly named log file.
scriptLogFile = logFile;
scriptLogFile = new File(app.layout.getUserSettingsDir(), "script.log");
}
LoggingInitialization.setApplicationLogFile(logFile);

View File

@@ -254,7 +254,7 @@ public class ClassSearcher {
long t = (new Date()).getTime();
log.trace("Searching for classes...");
log.info("Searching for classes...");
List<String> searchPaths = gatherSearchPaths();
searcher = new ClassFinder(searchPaths, monitor);