We currently go in-depth on the blade deploy command, but there are a few useful tidbits we can add to make it more informative:
- Gradle's default deploy task uses the auto-deploy mechanism, meaning the JAR is available in osgi/modules. This should be noted for those who prefer this way of deployment, which provides an easier undeployment method (remove JAR from folder).
- Blade's deploy command uses Gogo to add the module to the OSGi container. The only way to remove/undeploy a module that was deployed using Blade is to also use Gogo.
- There are two advantages to Blade's deploy command (inserts the module straight into the osgi/state/org.eclipse.osgi/BUNDLE_ID) over Gradle's deploy command (uses auto-deployer).
- It's faster.
- It can be used in any project, whereas the Gradle command is only callable from a workspace. Use the --base option to specify a base dir when specifying where to deploy a module.
- Blade can now deploy WAR files