arturobernalg opened a new pull request, #545: URL: https://github.com/apache/jspwiki/pull/545
Engine.findConfigFile only looked under WEB-INF and on the classpath, so jspwiki.policy.file=/some/dir/custom.policy was never found and the wiki failed to start with "Could not initialize local security policy". The filter configuration (jspwiki.filterConfig) already falls back to a plain file path; the policy file now works the same way, as findConfigFile returns the file when its name is the absolute path of an existing file. Names that are not absolute are resolved as before. Tests: 1 new case in AuthorizationManagerTest that starts an engine with a policy file in a temporary directory, given by absolute path, and checks that its grants are the ones applied. It fails without the change (the engine does not start). The jspwiki-util, jspwiki-event and jspwiki-main suites pass. I only ran it on Linux; the Windows part of the issue (C:/... paths) is not covered by a test. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
