All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
Wiki Markup |
---|
Much of the customisation described in the JSPUI and XMLUI customisation sections is based on [Maven WAR Overlays|http://maven.apache.org/plugins/maven-war-plugin/overlays.html]. In short, any classes or files placed in {{\[dspace-source\]/dspace/modules/\*}} will be overlayed onto the selected WAR. This includes both new and amended files. |
...
Wiki Markup |
---|
*Full Build:* Running {{mvn package}} from the root {{\[dspace-source\]}} directory |
Wiki Markup |
---|
This option will rebuild *all* DSpace modules from their Java Source code, then apply any [Maven WAR Overlays|#Maven WAR Overlays]. In other words, all subdirectories of {{\[dspace-source\]}} are recompiled/rebuilt. |
Wiki Markup |
---|
*Quick Build:* Running {{mvn package}} from the {{\[dspace-source\]/dspace/}} directory |
Wiki Markup |
---|
This option performs a "quick build". It does *not* recompile/rebuild all DSpace modules. All it does is rebuild and re-apply any [Maven WAR Overlays|#Maven WAR Overlays] to the previously compiled source code. In other words, the ONLY code that will be recompiled/rebuilt is code that exists in {{\[dspace-source\]/dspace/modules/\*}} (the Maven WAR Overlay directories) |
Wiki Markup |
---|
Which build option you need to use will depend on your local development practices. If you have been careful to utilize [Maven WAR Overlays|#Maven WAR Overlays] for your local code/changes (putting everything under {{\[dspace-source\]/dspace/modules/\*}}), then the *Quick Build* option may be the best way for you to recompile & reapply your local modifications. However, if you have made direct changes to code within a subdirectory of {{\[dspace-source\]}} (e.g. {{/dspace-api}}, {{/dspace-xmlui}}, {{/dspace-jspui}}, etc.) then you will need to utilize the *Full Build* option in order to ensure those modifications are included in the final WAR files. |