Question, when were the Avalon Jars last installed? If they were built by somebody other than me, there is a chance that they were not JDK 1.4 compliant then. I have used the classes compiled with JDK 1.4 in previous JDKs without problems.
The key is that the class compatibility must be set to 1.2 or 1.3--the serialization format has changed since then. The build is already set to make this happen. The Excalibur CVS is currently under surgery, breaking it into "smaller swords". We will still have the large jar available (currently at > 1M including all scratchpad files). Please bear with us.... > -----Original Message----- > From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 19, 2002 4:10 PM > To: [EMAIL PROTECTED] > Subject: Re: Code Freeze > > > I set incremental processing to false for Xalan in the sample > webapp because it was breaking the basic error generation samples. > > As for the release, we need to remember to make two releases, > one of which has the Avalon jars built using JDK 1.4 , for a > known issue with the database classes. Or even better make > one dist work with both JDKs. > > -- > Nicola Ken Barozzi [EMAIL PROTECTED] > - verba volant, scripta manent - > (discussions get forgotten, just code remains) > --------------------------------------------------------------------- > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
