I have found that when I launch OpenMRS locally using the Jetty server, it was possible for me to tweak the environment so that Maven (which am using to launch the web app via “mvn jetty:run”) is pointed to an alternative JDK/JRE 1.7. But, upon loggin into OpenMRS, checking the SystemInfo page shows that somehow, OpenMRS is still pointing to Java 8, which isn’t what I want.
So, my question: given that I launch maven from an environment exposing only Java 7, how is it that OpenMRS still reflects Java 8? Also, noticing as am launching OpenMRS from the webapp directory, how can one explicitly specify the desired JDK/JRE for OpenMRS given this directory doesn’t seem to contain any openmrs.properties file?
Am asking because there are some issues I ran into while attempting to run an OMOD. The deployment logs contain errors which the community history indicates are related to wrong JDK, thus the need to force OpenMRS to use JDK 7, but it’s proving to be tricky getting that working.
@dkayiwa while at it, I wonder, after looking at the documentation around the OpenMRS runtime properties file, there seems no hook to specify a custom JRE in that file. Is this something at all possible via some config file, or one has to rely on tweaking the JETTY/environment JRE?
Mr. Kayiwa, you’re right. The moment I tried to run “mvn jetty:run” with 7, it resulted in incompatibility issues as in this thread. They also recommend switching to 8, though it was the case that the mvn plugin docs mentioned 7 as well!
However, going back to the original issue - which is to tweak or adjust the JDK seen by OMRS, is it at all possible that we can still go back to an OMRS on 7, or is 8 the default/standard now?
OMRS is crazy! Chasing the original bug feels like running about in circles!
Not at any one moment did OMRS display JRE 7 on the UI. That’s what I was trying to aim at earlier in this streak. The case you mention is the default in all the tests I ran.