|
This section explains how to reinstall modules |
When developing a feature it is more than likely that you will need to go through a build, deploy, bind, configure, and test cycle multiple times to find any bugs. The recommended path to do this depends on whether you are updating a feature module that has no dependencies on it, or you are updating a profile or library that is depended on by other modules.
The starting point for both options assumes that all modules are currently deployed and bound into an active service.
Single Feature Module
Use this approach when you are working on a single feature that is in its own module and has no dependencies on it.
All ant commands should be run from in the feature module’s directory.
| Step | Action | Command | Notes |
|---|---|---|---|
1 |
Edit your feature code in an IDE and save it. |
||
2 |
Build and publish the feature. |
|
This compiles and publish your feature in the repository. If there are errors, they will be shown in this step. |
3 |
Redeploy your feature |
|
This will deactivate the services in which your feature is bound, unbind your feature, undeploy it, deploy the new published version, bind it and re-activate the service(s). |
|
First publish your feature, otherwise the redeploy will find the previously published version and install that, rather than your changed version. |
Profile, Library or Group Module
Use this approach when you are working on a profile or library that is in a module group, and is not depended on by any module outside of the module group. This is the common case for related features and their configuration profiles. All modules in the group need to go through the cycle, and this is supported with a slightly expanded version of the earlier approach. Assuming the following:
my-group-module (a directory containing one module with multiple modules in sub-directories) - build.xml - my-feature-module (a directory containing a module) - my-library-module (a directory containing a module) - my-profile-module (a directory containing a module) - ivy.xml - module.properties
All ant commands should be run from inside the my-group-module (i.e. the current working directory is my-group-module)
| Step | Action | Command | Notes |
|---|---|---|---|
1 |
Create or edit your feature in an IDE and save it. |
||
2 |
Build and publish the group of modules. |
|
This compiles and publishes all modules in the directory structure feature in the repository. If there are errors, they will be shown in this step. |
3 |
Redeploy your group of modules |
|
This will deactivate the services in which your modules are bound, unbind and undeploy the group of modules, deploy the newly published group of modules, bind them, and re-activate the service(s). |
|
|
Don’t forget to publish your group-module first, otherwise redeploy-all will find the previous version and install that. |
