> > >> >> That's the problem I hinted at in my first email. Doing it correctly >> we would have to build two versions of excalibur (1.2 compatible and >> 1.4 compatible) ourselfs! And this is something I really don't want >> to do. This would result in a real nightmare and which version do we >> keep in >> our CVS/lib directory? Can we assure that Excalibur is the only >> component we have to take >> into account? >> >> Now, making our lifes easier I'm in favour of building only a 1.2 >> compatible version (excalibur and all other projects are mostly >> build with a JDK 1.2 and not JDK 1.4). >> So we could make a binary distribution for 1.2,1.3 and that would even >> run with 1.4 except perhaps when it comes to JDBC. So anyone really >> requiring JDBC 3.0 has to build Excalibur and Cocoon himself. > > > Definately against this. > > Users with 1.4 will not be able to use the binary dist. Bleah :-P > Let's do them a favor, you compile it for them and call it dist-14. > Yes...thats yucky. 1 million emails of "gee it doesn't work" would ensue. Secondly, one must move forward not backward. Perhaps this is an opportunity, and maybe it points out a weakness in Excalibur that should be corrected. (just saying maybe)
-Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
