All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
Page History
The changes in 1.4.x releases are only code and configuration changes so the update is simply a matter of rebuilding the wars and slight changes to your config file.
...
| Info |
|---|
In the notes below |
[dspace-1.4.x-source |
...
] |
...
to |
...
the |
...
source |
...
directory |
...
for |
...
DSpace |
...
1.4.x. |
...
Whenever |
...
you |
...
see |
...
these |
...
path |
...
references, |
...
be |
...
sure |
...
to |
...
replace |
...
them |
...
with |
...
the |
...
actual |
...
path |
...
names |
...
on |
...
your |
...
local |
...
system. |
Upgrade Steps
The changes in 1.4.x releases are only code and configuration changes so the update is simply a matter of rebuilding the wars and slight changes to your config file.
- Get the new DSpace 1.4.x 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 Blockpanel cd
[dspace]/lib
cppostgresql.jar
[dspace-1.4.x-source]/lib
Wiki Markup - Note:* Licensing conditions for the _handle.jar_ file have changed. As a result, the latest version of the _handle.jar_ file is not included in this distribution. It is recommended you read the [new license conditions|http://www.handle.net/upgrade_6-2_DSpace.html|new license conditions] and decide whether you wish to update your installation's _handle.jar_. If you decide to update, you should replace the existing _handle.jar_ in _\[dspace-1.4.x-source\]_/lib with the new version.
- Take down Tomcat (or whichever servlet container you're using).
- A new configuration item webui.html.max-depth-guess has been added to avoid infinite URL spaces. Add the following to the dspace.cfg file:
If webui.html.max-depth-guess is not present in dspace.cfg the default value is used. If archiving entire web sites or deeply nested HTML documents it is advisable to change the default to a higher value more suitable for these types of materials.unmigrated-wiki-markupCode Blockpanel ####
Multi-file
HTML
document/site
settings
#####
#
#When
serving
up
composite
HTML
items,
how
deep
can
the
request
be
for
us
to
#serve
up
a
file
with
the
same
name?
#
#e.g.
if
we
receive
a
request
for
"foo/bar/index.html"
#and
we
have
a
bitstream
called
just
"index.html"
#we
will
serve
up
that
bitstream
for
the
request
if
webui.html.max-depth-guess
#is
2
or
greater.
If
webui.html.max-depth-guess
is
1
or
less,
we
would
not
#serve
that
bitstream,
as
the
depth
of
the
file
is
greater.
#
#If
webui.html.max-depth-guess
is
zero,
the
request
filename
and
path
must
#always
exactly
match
the
bitstream
name.
Default
value
is
3.
#
webui.html.max-depth-guess=
3
- 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.4.x versions into your locally modified ones. You can use the _diff_ command to compare your JSPs against the 1.4.x versions to do this. You can also check against the [DSpace CVS|http://dspace.cvs.sourceforge.net/dspace/].unmigrated-wiki-markup
- In _\[dspace-1.4.x-source\]_ run:
Code Blockpanel ant
-Dconfig=
[dspace]/config/dspace.cfg
update
Wiki Markup - Copy the _.war_ Web application files in _\[dspace-1.4.x-source\]/build_ to the _webapps_ sub-directory of your servlet container (e.g. Tomcat). e.g.:
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.Code Blockpanel cp
[dspace-1.4.x-source]/build/*.war
[tomcat]/webapps
Wiki Markup - Restart Tomcat.
Overview
Content Tools