On Sat, Mar 8, 2014 at 7:50 PM, Schuster, David <[email protected]> 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] https://ideals.illinois.edu/handle/2142/11915


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to