[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mifos-developer
Subject:    Re: [Mifos-developer] [PATCH] initial changes to run
From:       "Jim Kingdon" <jkingdon () grameenfoundation ! org>
Date:       2006-12-12 22:47:13
Message-ID: 9DD845C1ED0D5D40B4B56DF5A4B1EB0E0119082B () gfmail ! gfusa ! org
[Download RAW message or body]

> The separate buildfile sounds like a good initial solution.

Sounds good to me.  Should be possible for it to be pared down
enough that it doesn't duplicate much of build.xml, I hope.

> One option mentioned in the technical ToDos wiki would be to include
some
> tools used by the Mifos build under svn.  The plus side to including
tools
> there would be that they could be preconfigured and referenced from
the
> build file.

I've certainly imagined doing this for Jetty and Derby (or some other
pure Java database).  Maybe it is the right solution for findbugs, I
don't know.

You are right about some of the downsides to checking in
everything under the sun.  In addition sometimes things like
unpacking a tool might be slow (depending on the nature of the
tool and how the build scripts work).  I suppose the whole thing
depends on things like how big the tool is.


[prev in list] [next in list] [prev in thread] [next in thread]