On Sep 11, 2007, at 11:42 PM, David Ward wrote:
Vincent,
I'm not sure if this is the email you were referring to.
No sorry it was another one but I replied to the old list... so just
resent it this morning...
-Vinent
For Curriki, I think as long as there is an easy (and
constant) way to
add the driver and configuration to the war via a script (such as
unjar, copy files, jar) then this sounds fine to me.
Right now this is how the xwiki.cfg, hibernate.cfg.xml, and web.xml
files get added on our development system before giving to Sun's SJSAS
for auto-deployment after each successful build.
Dave
--
On 9/6/07, Vincent Massol <vincent(a)massol.net> wrote:
> Hi,
>
> I'm proposing to improve the generic install to add database
> configuration setup:
>
> 1) include different database driver jars in the installer
> 2) have some installation panels to let the user choose the database
> to use (using some combo box and fields to modify default DB values)
> 3) include the XAR in the installer
> 4) use the packager tool to import the XAR in the database at install
> time (using the information provided in 2))
>
> Note: I'd also like to modify the web/standard build so that we
> release only a single WAR without database driver and without DB
> configuration.
>
> Advanced users will configure it manually and novice will use the
> installer.
>
> WDYT?
>
> Thanks
> -Vincent