The maven "magic" happens when you put these customizations in the /dspace-src/dspace/modules directory

Some more detail on this can be found in this deck of slides: (especially slide 12)



Bram Luyten +1 202 684 6365
2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010
Esperantolaan 4, Heverlee 3001, Belgium 

On Sun, Mar 9, 2014 at 5:42 AM, Schuster, David <> wrote:
So if I make changes to dspace-source when I do the next upgrade they will be recognized?  I'm pretty new to this so it is still magic to me when it happens.

Most of my if not all of them are cosmetic so easy to reimplement but just looking down the road to easier upgrades.

The tomcat and Catalina caching I believe is what maybe threw me off with this upgrade.  Seeing 3.1 after upgrades when everything seemed to go ok.  Just my themes hadn't been updated...

Sent from my iPhone

> On Mar 8, 2014, at 1:10 PM, "helix84" <> wrote:
>> On Sat, Mar 8, 2014 at 7:50 PM, Schuster, David <> wrote:
>> It looks like I wasn't updating the themes right or tomcat as when I removed files in the tomcat rebuilt and then opened it I see 3.2.  Now to identify those changes I made in 3.1 and reimplement.  I'm documenting those changes for future reference.
>> I presume that is why you are supposed to make changes to source and run ant?  How will those changes get reimplemented in 4 or will I have to reimplement them again?
> That depends on the type of changes. Changes to themes can be made in
> the [dspace]/webapps/xmlui/themes/ directory as long as you remember
> during upgrades/rebuilds that you didn't put them into [dspace-src].
> Same goes for configuration changes.
> As far as themes go, my recommendation is to make a minimal skeleton
> custom theme that inherits all the XSL templates from its parent theme
> and only keep your template overrides in it. That way you get free
> updates to the base theme during any DSpace upgrade. Of course, you
> still have to port any changes to the templates you customized
> manually. But I've yet to write extensive documentation on this
> method.
> Any changes to .java source files are recommended to be made as
> overlays (see [1]) so that you can easily see what changes you made
> and update them as needed for the new version. Alternatively, if you
> prefer to use a version control system for keeping track of changes, a
> diff between the unmodified and customized source of the same version
> would serve the same purpose. In both cases you need to run both maven
> and ant to build and deploy such changes.
> [1]
> Regards,
> ~~helix84
> Compulsory reading: DSpace Mailing List Etiquette