152 | | The easiest way to let DeepaMehta hot-deploy the plugin is to develop it within the **`bundle-dev`** directory. To start doing so move the plugin directory on your hard disc into DeepaMehta's hot-deployment folder called **`bundle-dev`**. The next step is to build your plugin. |
153 | | |
154 | | Another way to let DeepaMehta hot-deploy the plugin is in DeepaMehta's **`pom.xml`**: add the plugin's `target` directory (here: `/home/myhome/deepamehta-dev/dm4-tagging/target`) to the `felix.fileinstall.dir` property. Important: make sure your line ends with a comma: |
155 | | |
156 | | {{{ |
157 | | #!xml |
158 | | <project> |
159 | | ... |
160 | | <felix.fileinstall.dir>, |
161 | | ${project.basedir}/modules/dm4-core/target, |
162 | | ${project.basedir}/modules/dm4-webservice/target, |
163 | | ${project.basedir}/modules/dm4-webclient/target, |
164 | | ... |
165 | | ${project.basedir}/modules/dm4-storage-neo4j/target, |
166 | | /home/myhome/deepamehta-dev/dm4-tagging/target, |
167 | | </felix.fileinstall.dir> |
168 | | ... |
169 | | </project> |
170 | | }}} |
171 | | |
172 | | Now start DeepaMehta. In the directory `deepamehta` (where you've build): |
| 152 | The easiest way to let DeepaMehta hot-deploy the plugin is to develop it within the **`bundle-dev`** directory. To do so move the plugin directory on your hard disc into DeepaMehta's hot-deployment folder called **`bundle-dev`**. The next step is then to build your plugin. |
| 153 | |
| 154 | But lets first start DeepaMehta in development mode, that is with hot-deployment activated. |
| 155 | |
| 156 | In the platforms home directory `deepamehta`: |