THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
If you have created you assemblies, service units, components and shared libraries as Maven projects (which all ServiceMix components are) you can use this goal. In essence the plugin will walk the dependencies starting in the current project then deploy each of the dependencies in reverse order. This can be very useful if you want to quickly get up and running with a new Service Assembly against an installed instance of Apache ServiceMix.
| Info | ||
|---|---|---|
| ||
If you are working with the jbi:projectDeploy you should not that you may want to disable dependency deployment, if you are deploying to a server which has other components sharing these dependencies they you can get problems while trying to undeploy and redeploy them. If this is the case you can add the parameter deployDependencies at set it to false in either you service assembly or component pom.xmlLook for the plugin section for the jbi-maven-plugin and under configuration add a new element called deployDependencies with a value of false, this is usually in your service assembly's pom.xml or your component's. This setting will stop the plugin for undeploying and redeploying dependencies. |
mvn jbi:servicemix
If you quickly want to get up and running with Apache ServiceMix the best way is to use this goal. As an extension of the deployProject goal is works in much the same way, the difference is that this goal downloads and starts a copy of Apache ServiceMix within Maven so you don't need to have a version installed, this can be very useful if you are working on trying out functionality and want to simply test your projects.
...