I am making some changes in view of patient registeration page i.e. (registerPatient.gsp), which when deployed gets displayed as .page file. Now each and every time I make any change in registerPatient.gsp (view) I have to redeploy registeration module.
Can someone please tell is there an easy way of doing this to esacpe redeploying the module again and again?
@dkayiwa Hi I have taken the below steps to start into developement mode.
Note:- I am running it on windows.
Cloned registeration module into " C:\Projects\code\openmrs-module-registrationapp"
Start the tomcat with passing variable arguments from command line
C:\Projects\apache-tomcat-9.0.0.M15\bin>startup.bat -DuiFramework.development.registrationapp=“C:\Projects\code\openmrs-module-registrationapp”
Then tried to make changes in registerPatient.gsp( in openmrs cache) file, but there was no effect
I mean that after deploying the registeration module into openmrs, the changes I am doing in registerpatient.gsp page is in the cache (C:\Projects\apache-tomcat-9.0.0.M15\bin\openMRSAppData.openmrs-lib-cache\registrationapp)
That will not work.
The automatic reloading works with changes made directly from the original source, not that cache.
Where the original source is the path you specified with -DuiFramework.development.registrationapp
We generally discourage private calls and chats for public conversations. We always want as many as possible to learn from the conversations. So i would recommend that you use the public openmrs irc channel https://wiki.openmrs.org/display/IRC/Home
That being said, you are using the hardest and longest path for development changes testing.
While in eclipse, right click on the webapp project and select Run As -> Maven build…
In the windows that shows up, under Goals put: jetty:run
Then go to the JRE tab and paste in the VM arguments before you click Run