> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] > > Vadim Gritsenko wrote: > > > > Ditto. Just make sure that Excalibur is built with appropriate version > > too - it has JDBC code too. > > > 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.
Nobody really wants :) > This would result in a real nightmare and which version do we keep in > our CVS/lib directory? JDK 1.2 compatible. > Can we assure that Excalibur is the only component we have to take > into account? ATM, and AFAIK, yes. > 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). I would -1 for following reasons: Since release of 1.4, more and more users for one or another reason move to the JDK1.4. It is real PITA to build Excalibur for developer, and it is double to infinite PITA for the (end) users. Since release 2.0.2, JDK1.4 issue is the issue most of the users complain about and solution to it alone (like two distributions) is good enough reason to make 2.0.3, even if no other changes done. > 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. If you go with this approach, do at least write really clear and working document on how it is possible for the end user to make working (under JDK1.4) version of Cocoon without using CVS. PS While we are at this issue... Can you also compile excalibur with InformixDataSource included? This would close http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8875. Vadim > Comments? > > Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
