> - Which taglib jar must be shipped? (one provides all features, but > doesn't work in tomcat 4, the other one is more conservative). More > or less it was decided to ignore tomcat 4 compatibility. Still that > needs to be arranged in the build. I would go for the advanced one, I would also like us to have the best support for java 1.5 by including xerces and ecluding the collections backport.
> - Must rmmci be installed in the distro? I think the RMMCI package, does > contrary to other packages not contain a directory. Perhaps I can write a webstart app so that rmmci is actualy used somewhere? > - Apps 1 import/export. Does it work properly? Also for new-style > builders and so on? This must be tested, and ensured that it works. I > don't think that it does. If it cannot be made to work perfectly, at > the very least this must be stated somewhere. I agree. > - Code-reviews. Could perhaps be considered as no show-stopper, because > I think the workings are tested. But there are many new classes in > e.g. org.mmbase.datatypes, org.mmbase.core, org.mmbase.cache, > org.mmbase.core.events > which have not been reviewed or judged by anyone besides the original > author(s). I feel that a situation arises in which we have to say 'speak > now, or remain silent for ever!'. Perhaps it is not wise to make major > changes in much code on these terrains, but perhaps it is not too late > to mark code on which people have doubts as 'experimental!' or as > 'possibly subject to future changes!' Its a shame I did not spend much time with mmbase 1.8 perhaps its enough if people that already use it state there comments -did you create new data types? -did you migrate from mmbase 1.7 -have you ruun mmbase 1.8 clustered? > - CommandServer for image-magick. Using this would avoid the problems > arising from the fork done by the JVM for the Runtime.exec. is that a small mmbase server? greetings _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
