On Thu, Aug 1, 2013 at 6:07 PM, Guillermo Esteban Murillo Goussen <[email protected]> wrote: > First I found one of the Mirage.xsl files (there are like seven) at > dspace-3.1-src-release/dspace/modules/xmlui/target/war/work/org.dspace/dspace-xmlui/themes/Mirage/Mirage.xsl. > I guess it is the one to modify.
No, that's not the right one. Never modify anything in any "target" directory. That is just an intermediate step - it's created by "mvn package" from [dspace-source] and the files from [dspace-source]/whatever/target are copied to [dspace] during the "ant update" phase. When you're developing and testing your modifications, it's easiest to simply modify the XSL in [dspace]/webapps/xmlui/themes/Mirage/Mirage.xsl, the changes will be visible upon page reload (if not, see [1]). That's also where your template overriding dri:body should go. (The official recommendation is to do all changes in [dspace-source], because during mvn package/ant update, the webapps in [dspace] are replaced by those from [dspace-source]. But fear not, the old ones are kept in [dspace]/webapps.bak-[date_and_time_of_ant_update].) [1] https://wiki.duraspace.org/display/DSPACE/TechnicalFaq#TechnicalFaq-ClearingCocoon(XMLUI)cache Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&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
