On Nov 21, 1:57 pm, Adam Monsen <[EMAIL PROTECTED]> wrote: > On Nov 21, 12:49 pm, Kimloan Ho <[EMAIL PROTECTED]> wrote: > [...]> The reason the /test needs > > applicationConfiguration.custom.properties is because > > some of the set up for test is not standards for Mifos > > so it can't be in the > > applicationConfiguration.default.properties but it > > needs for the test. > > [...] > > Right, I understand. The test configuration is different than the > production configuration. > > Looks like applicationConfiguration.default.properties from src/ is on > the classpath during the unit tests (because it is copied into build/ > src_pkg/WEB-INF/classes/org/mifos/config/resources), and this is why > applicationConfiguration.custom.properties must be used in the test/ > dir. Not ideal, but at least I understand what's going on. > > I think it should be possible to use a blank > applicationConfiguration.default.properties in test/ ...I'll try this > out and--if it works--add a comment to that file explaining why it is > blank. > > > > I see that, but if someone did create one, it should > > > never be checked > > > into source code control, right? Or am I missing > > > something? > > > That's right. [...]
Having a blank .default.properties in test/ works. Here's a small patch to enforce good programming practice as described above. http://adammonsen.com/tmp/appcfg.patch.gz -- Adam Monsen ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
