-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added solr startup check. Refactored to make props available #1656
Conversation
… and future checks. Added tests
|
||
// can read? | ||
defaultProperties.load(Files.newBufferedReader(defaultPropsFilePath)); | ||
// can write? Use isWriteable() so we don't mess up props file formatting for Jing :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. But the metacat.properties file is still changed :). I believe it happens when we write some properties (such as status) into the file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed - I just thought I would be better not to have it happen in yet another place :-)
|
||
Properties siteProperties = new Properties(); | ||
runtimeProperties = new Properties(defaultProperties); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any reason why we need the defaultProperties
to initialize the runtimeProperties? If we just use the default constructor to initialize the runtimeProperties object, we can only has one parameter in the method signature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thank you!
see #1631