On Mon, Aug 5, 2013 at 2:42 PM, Clive Gould <[email protected]> wrote: > Thanks for the suggestions. I've tried everything including mvn, ant and > subsequently manually replacing every reference to ${dspace.dir with > /home/dspace in all files in /home/dspace/config and its subdirectories
Like Kostas mentioned in another thread, yet another place where these variables are used is in web.xml files in each webapp. But I don't understand where the problem could be - if you made sure dspace.dir has an actual value in [dspace-source]/dspace/config/dspace.cfg before running "mvn package", then the change should propagate everywhere during "ant update". You can try "mvn clean package" instead of "mvn package", but I don't think it should make a difference. 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
