Well, now I see why I was confused. ConfigurationManager defines a system property "dspace.configuration", which it will use, if defined, in preference to consing up a path to config/dspace.cfg. The Configuration Service does not do this.
The testing framework depends on dspace.configuration to let it build
an augmented dspace.cfg elsewhere and use that configuration instead
of config/dpsace.cfg. Tests which use ConfigurationManager will use
that alternate configuration, but as soon as something touches the
Configuration Service, it will use the "default" configuration, which
still contains "dspace.dir = ${dspace.dir}" and we begin, as a
colleague puts it, an empirical investigation of the Halting Problem.
I find -Ddspace.configuration to be a useful feature. I think it
should be ported over to the Configuration Service, and I volunteer to
do the work. It shouldn't take long.
Comments?
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Asking whether markets are efficient is like asking whether people are smart.
pgpukCFKSD6ue.pgp
Description: PGP signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
