I must be missing something here. Even with a fresh server (i.e. one
that's never had DSpace installed on it previously), I can't seem to
customise the source of v3.2 (Stable).
Specifically, all I'm trying for my santity test is in the file:
dspace-3.2-src-release/dspace-api/src/main/java/org/dspace/core/ConfigurationManager.java
Changing the line:
info("Loading provided config file: " + configFile);
to
info("Loading provided config file. I was here.graffiti: " + configFile);
However, following a:
mvn clean package
and then a
ant fresh_install (in the directory
build/dspace-3.2-src-release/dspace/target/dspace-3.2-build/)
and tailing catalina.out, I see the original unmodified INFO string, i.e.:
Loading provided config file:
in the logs (rather than my customised version from above).
Does some 'magic' happen with the Stable releases (e.g. download of a
precompiled WAR or something) ?
Have tried a few times on this server, and I don't have any NFS mounts
etc whereby there could be old (cached) files, so am perplexed...
Thanks in Advance,
Patrick Rynhart
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees_APR
_______________________________________________
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
