Relative path reference to version.properties
Description
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:

Markus von Rüden December 7, 2017 at 2:38 PM
Fixed
Assignee

Reporter

Fix versions
Priority
Created December 7, 2017 at 2:24 PM
Updated December 8, 2017 at 2:37 PM
Resolved December 8, 2017 at 2:37 PM
When you try to start the opennms binary from a different location than ${OPENNMS_HOME} the version.properties is tried to be loaded from the current directory instead of ${OPENNMS_HOME}.
This will have several side effects where the version information in ReST API is evaluated for example in Grafana. The version string is empty and the capabilities can't be correctly evaluated.