I'm in favor of an installer but I'd suggest keeping it separate from the
webapp itself; I may not be grasping the rationale for putting it in the
webapp.
Regarding the dbscripts, I'm indifferent about whether they should be in the
WEB-INF or not, but it's confusing to have the second incomplete set, so we
should clean that aspect up.
--a.
----- Original Message -----
From: "Dave" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, May 13, 2007 6:46 PM
Subject: Re: dbscripts in trunk
On 5/13/07, Allen Gilliland <[EMAIL PROTECTED]> wrote:
That may be something that I did, but it's something we need to sort out
so that it works the way we want.
I added in an ant target for "gen-dbscripts" which creates all the db
scripts and puts them in build/dbscripts and i know that is working
properly. The old build process used to build them directly to
WEB-INF/dbscripts but I think that doesn't make much sense. Users
shouldn't have to descend into the webapp dirs to get the db script
files, I think they should be a top level directory of the packaged
releases.
True, users shouldn't have to dig down deep to find them.
But I'm working on plans for improving the Roller installation process
and part of the plan is to have Roller itself sense that tables are
missing or in need of update and to offer to automatically
create/update them if needed. For that to work, the webapp will have
to be able to easily find those scripts and keeping them in dbscripts
is one way to do that.
- Dave
