On Tue, Feb 02, 2016 at 08:42:15PM -0500, Luiz dos Santos wrote: > Since today afternoon I'm build Maven and run ant targets with the new > local.cfg, dspace-pre-6, but the dspace.cfg doesn't reflect the changes > that I did in the file local.cfg, the maven and ant go through without any > error, so I wonder if anybody else is getting this issue?
That's the way it should be. Installation should copy dspace.cfg and local.cfg as-is; dspace.cfg is no longer filtered in the way that used to be done using build.properties. At runtime, DSpace will load *both* of these files into the in-memory configuration, and local.cfg settings will override those in dspace.cfg. So what you should see is that the installed DSpace instance contains both config/dspace.cfg and config/local.cfg with content as it was in the source tree, and the running DSpace behaves according to the settings in local.cfg that have the same names as settings in dspace.cfg. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
