I got 1.4.1 running on production today. Had the same problem I had upgrading on test—missed something (don’t even know what!) in the configuration file.
When this happens, for future reference, DSpace throws a wobbly and refuses to run at all, popping up a NullPointerException in ConfigurationManager.java. That’s a great hint that dspace.cfg is the problem. Unfortunately, it tells you absolutely nothing about which part of dspace.cfg is at fault—and dspace.cfg is nearly 700 lines long now.
(Configurationitis is going to become a problem for DSpace’s out-of-the-boxness, if it isn’t one already. If I were a committer, I’d be taking a hard look at how many of these config items can be handled another way, or even better, replaced entirely by sensible system defaults. “Throw in a config option!” is frequently the worst way to resolve a squabble about a development choice.)
But. It’s running. And our modded code is safely in Subversion. Mission accomplished.
