|
2 | 2 |
|
3 | 3 | * Increase the maven memory: e.g. export MAVEN_OPTS="-Xms1012m -Xmx2024m" |
4 | 4 | * mvn clean |
5 | | -* mvn package -Dopenmrs.version=2.8.0-SNAPSHOT -Drefapp.version=2.14.0-SNAPSHOT |
6 | | -* You can also use mvn package to build the default version on openmrs.version=2.8.0-SNAPSHOT and refapp.version=2.14.0-SNAPSHOT |
| 5 | +* mvn package -Dopenmrs.version=2.7.4 -Drefapp.version=3.4.0 |
| 6 | +* You can also use mvn package to build the default version on openmrs.version=2.7.4 and refapp.version=3.4.0 |
7 | 7 | * If running a second time, ALWAYS check to make sure mysql processes on port 3326 and 3328 are stopped. |
8 | 8 | If you DON'T do that, then the "mvn clean" will not really clean. |
9 | 9 | A good command to use is: "pkill -f standalone" (kills anything with "standalone" in the path) |
|
16 | 16 | - Copy your war file into the "tomcat/webapps" folder. Where the tomcat folder is at the root of the project. |
17 | 17 |
|
18 | 18 | If you already have openmrs installed and do not want to interfere with it, just rename |
19 | | -your war file to something different from openmrs.war. Examples are openmrs-2.8.0-SNAPSHOT.war, etc which suppoort Java 17 and above. |
| 19 | +your war file to something different from openmrs.war. Examples are openmrs-2.7.4.war, etc which suppoort Java 17 and above. |
20 | 20 |
|
21 | 21 | - Right click on the project and select Run As -> Run Configurations |
22 | 22 |
|
@@ -73,7 +73,7 @@ The release/distribution (end user) folder structure should look like this: |
73 | 73 | NOTE: Without this folder structure, you will get errors while trying to run the standalone application. |
74 | 74 |
|
75 | 75 | * contextname-runtime.properties |
76 | | - * e.g openmrs-runtime.properties, openmrs-2.14.0-SNAPSHOT-runtime.properties, etc |
| 76 | + * e.g openmrs-runtime.properties, openmrs-3.4.0-runtime.properties, etc |
77 | 77 | * If you want to use this runtime properties file, make sure that the web application context name does not match with any existing runtime properties file in say the user's home folder. This is because of the openmrs runtime properties file search order which will only look in the current application folder as the last resort if no runtime properties file has been found in any of the other possible locations. |
78 | 78 | * standalone.jar |
79 | 79 | * This is the output executable jar for this standalone project. |
@@ -152,7 +152,7 @@ browser Use to launch a new browser instance. |
152 | 152 | 4- The application will start the tomcat server and then the mariadb4j database engine. |
153 | 153 | 5- Follow the steps in the openmrs setup wizard to select where you want the demo database distribution or ciel database distribution to be created. |
154 | 154 | 6- After the setup wizard is done, you will have a database created in the location you selected. |
155 | | -7- Open your browser and go to the openmrs setup wizard at http://localhost:8080/openmrs |
| 155 | +7- Open your browser and go to the openmrs setup wizard at http://localhost:8080/openmrs/spa |
156 | 156 | NOTE: The default location of the "database" folder is that where the standalone.jar file is. |
157 | 157 | You should also add the application_data_directory key to the runtime properties file. Something like this: |
158 | 158 | application_data_directory=appdata |
|
0 commit comments