> No, I really meant
> applicationConfiguration.custom.properties. Based
> on the content of configurationFactory.xml, it
> appears that
> applicationConfiguration.custom.properties is an
> "optional" file, I'm
> assuming (possibly incorrectly?) in the fashion that
> conf/
> my.build.properties optionally contains overrides of
> properties in
> conf/build.properties. Am I on the wrong track?
The applicationConfiguration.default.properties should
always be there and if users want to override with
their values they can do so in the
applicationConfiguration.custom.properties. 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. For example, when the tests were
written the working days in the database is
Monday,...,Sat. But when the test starts the working
days is update in the database to be
Monday,...,Sunday. That is why the custom properties
is needed for the test.
> 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.
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
