I tested the mmbase release on windows 98, with Orion 1.5.2, using (or attempting to use) the default database, hsldb.

The following findings are for the release team.

- The binary distro (bindist target) copies all the builders from included applications to the builder dir. this means that all these buidlers are amde active by default, generating a lot of builders people will likely not use initially (such as bugreports, community buidlers, etc.)
I think it is not desirable to do this. My proposal: remove current builders that are specific to an application (i.e. bugtracker and community), and instead let the applications install these builders.
Activate a number of basic builders, but leave the rest either inactive, or remove from cvs. I also propose to drop a number of very vague builders that are not used anywhere (i.e. videoparts).

- jars that are needed (xalan, xerces, log4j, etc.) are not included in the distro zip. People have to obtain it themselves. I think these jars have either to be included or should be available in an easy way (i.e.as a downloadable zip).

- MMBase uses a default database in its config, but does not include a jdbc driver for it. Maybe it's desirable to add the hsqldb.jar to the lib dir in the binary release.

- Jumpers does not work in orion. 9 out of 10 question on IRC seem to be about problems with jumpers. I propose to turn jumpers off by default. Remove the builder from the builders dir, let the application install it. Comment out (but otherwise leave intact, so it can easily be turned on) jumper filter config in web.xml. Add to the application instructions on how to turn the filter on.

- Some builders didn't have size specified for some text fields. This cause sproblems in hsqldb and hypersonic. Fixed it for community builders but have to check other builders.

So far

--
Pierre van Rooden
Mediapark, C 107 tel. +31 (0)35 6772815
"Never summon anything bigger than your head."


Reply via email to