Ben, the deploy path says where OpenMRS is deployed. It should point either to a directory in Tomcat or like in that case to where jetty looks for file changes. There's no reasonable default here. In the example I used a relative path, but it could be an absolute path as well. The relative path is from module/omod. I'll add this explanation to the wiki.
-Rafal On 1 February 2012 19:58, Ben Wolfe <[email protected]> wrote: > Very cool. I know at least a few people have been waiting for this. > > In the wiki page you said the command should be used thusly: > mvn package -Pdeploy-web -Ddeploy.path= > "../../openmrs-1.8.x/webapp/src/main/webapp" > > Is the path always needed? Does it use the current dir (or at least > src/main/webapp) as default, assuming the user is in /webapp? > > Ben > > On Wed, Feb 1, 2012 at 12:02 PM, Rafal Korytkowski <[email protected]>wrote: > >> Hey, >> >> To make developing modules easier we've created a profile that should be >> added to poms in modules. It's a maven replacement for the deploy-web ant >> target and it allows to deploy module web resources without re-installing a >> module. It should be added to the maven module conversion script and the >> maven module archetype. I can take care of the latter. >> >> For more details see: >> https://wiki.openmrs.org/display/docs/Creating+Modules >> >> -Rafal >> ------------------------------ >> Click here to >> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >> OpenMRS Developers' mailing list > > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
