Page History
...
Info | ||
---|---|---|
|
Upgrade Steps
The changes in 1.3.2 are only code changes so the update is simply a matter of rebuilding the wars.
- Get the new DSpace 1.3.2 source code from the DSpace page on SourceForge and unpack it somewhere. Do not unpack it on top of your existing installation!!
- Copy the PostgreSQL driver JAR to the source tree. For example:
Code Block cd [dspace]/lib cp postgresql.jar [dspace-1.3.2-source]/lib
- Take down Tomcat (or whichever servlet container you're using).
Wiki Markup Your 'localized' JSPs (those in jsp/local) now need to be maintained in the _source_ directory. If you have locally modified JSPs in your _\[dspace\]/jsp/local_ directory, you will need to merge the changes in the new 1.3.2 versions into your locally modified ones. You can use the _diff_ command to compare the 1.3.1 and 1.3.2 versions to do this.
Wiki Markup In _\[dspace-1.3.2-source\]_ run:
Code Block ant -Dconfig= [dspace]/config/dspace.cfg update
Wiki Markup Copy the _.war_ Web application files in _\[dspace-1.3.2-source\]/build_ to the _webapps_ sub-directory of your servlet container (e.g. Tomcat). e.g.:
Code Block cp [dspace-1.3.2-source]/build/*.war [tomcat]/webapps
Wiki Markup If you're using Tomcat, you need to delete the directories corresponding to the old _.war_ files. For example, if _dspace.war_ is installed in _\[tomcat\]/webapps/dspace.war_, you should delete the _\[tomcat\]/webapps/dspace_ directory. Otherwise, Tomcat will continue to use the old code in that directory.
- Restart Tomcat.
Overview
Content Tools