Date: Thu, 28 Mar 2024 12:48:36 -0400 (EDT) Message-ID: <349939357.28396.1711644516474@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_28395_91889687.1711644516473" ------=_Part_28395_91889687.1711644516473 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
It is anticipated that the customisation features described in t= he JSPUI and XMLUI customisation sections will be sufficient to satisfy the= needs of the majority of users, however, some users may want to customise = DSpace further, or just have a greater understanding of how to do so.
This module was added in DSpace 3.0 and should be used to store dspace-a=
pi changes, custom plugins, ... Classes placed in [dspace-source=
]/dspace/modules/additions
will override those located in the dspace=
-api. This module will be used for all the webapps located in the
Much of the customisation described in the JSPUI and XMLUI customisation=
sections is based on Maven WAR Ov=
erlays. In short, any classes or files placed in [dspace-source]/=
dspace/modules/*
will be overlayed onto the selected WAR. This inclu=
des both new and amended files.
For more details on Maven WAR Overlays and how they relate to DSpace, se=
e this presentation from Fall 2009: Making DSpace XMLUI Your Own
(Please note that this presentation was made for DSpace 1.5.x and 1.6.x, b=
ut much of it still applies to current versions of DSpace.)
If you have downloaded the 'dspace-src-release' (or checked out the late= st DSpace Code via GitHub), there are two main build options= that are available to you:
mvn package
from the =
root [dspace-source]
directorymvn package
from the=
[dspace-source]/dspace/
directory[dspace-source]/dspa=
ce/modules/*
(the Maven WAR Overlay directories)Which build option you need to use will depend on your local development=
practices. If you have been careful to utilize 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 mad=
e direct changes to code within a subdirectory of [dspace-source] (e.g.
/dspace-api
, /dspace-xmlui
, /dspa=
ce-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.