On Jul 11, 2007, at 12:51 AM, Sergiu Dumitriu wrote:
+1 for option 3. Indeed, if a user finds it hard to
configure the
database, then he should use the standalone package.
Yes, and I have now started an installer package in which we could
let the user decide its database option on a screen and in which we
could package the different JDBC drivers.
-Vincent
On 7/10/07, Vincent Massol <vincent(a)massol.net> wrote:
Hi,
With the 1.1M3 release we have currently only released a hsql version
of the platform WAR. That war only includes the HSQL JAR but not the
driver JARS for other DBs.
In our current build we can generate the platform WAR for other DBs
using for ex: mvn install -Pmysql. That includes the driver JAR for
that DB.
Before we were bundling all driver JARs into our WAR so our users may
be a bit confused and we need to decide on the strategy we want to
have. I can see 3 possible strategies:
1) 1 WAR per database
- We could start by releasing only 2 WARs: one for HSQL and one for
MySQL. I don't think we need more and releasing more is going to be a
pain as each WAR weights 40MB.
2) 1 WAR with everything
- Cons: having all these DB drivers makes our WAR fatter
- Possible solution: we only release the HSQL and MySQL drivers
3) 1 empty WAR
I feel 3) might actually be the best solution for the following
reasons:
- if the user is non technical he'll install the standalone version
- if the user is technical it means he shouldn't have any problem
following install instructions that tell him to download such driver
at such location and put it in WEB-INF/lib
- we only release one common WAR and our XWiki Platform is
environment independent (which is a new property to have I think)
- releasing one WAR makes our release process simpler (only 40MB to
release once)
WDYT?
Thanks
-Vincent
Sergiu
--
http://purl.org/net/sergiu