Re: [Htmlparser-developer] ParserTestCase - JDK 1.4
Brought to you by:
derrickoswald
From: Derrick O. <Der...@ro...> - 2003-05-09 22:08:49
|
Version 1.13 of this file dropped May 2nd fixed this: 'remove JDK 1.4 isms' dha...@or... wrote: >The assertStringValueMatches() method in ParserTestCase contains >reference to String.replaceAll() method which I believe is introduced in >JDK 1.4. Can you please remove the same? > >Regards, > >Dhaval Udani >Senior Analyst >M-Line, QPEG >OrbiTech Solutions Ltd. >+91-22-28290019 Extn. 1457 > > > >-----Original Message----- >From: DerrickOswald [mailto:Der...@ro...] >Sent: Friday, May 09, 2003 9:49 AM >To: htmlparser-developer >Cc: DerrickOswald >Subject: [Htmlparser-developer] changes.txt > > > >OK, I'm going to try using the cvs2cl script to automatically create the > >change log for a release. > >That means you don't have to update changes.txt when you drop code. >yeaahhh! > >But, you do have to make the commit messages as good or better than the >changes.txt message was. boooo! > >For guidelines on what to put in commit messages see: > http://www.red-bean.com/cvs2cl/changelogs.html >Remember, the commit messages will now be visible to end users, so try >to use whole sentences and valid grammar. > >Also, the script uses a time window and identical message text to unify >separate file log messages into a chronological sequence of activity. >So, the rule is, drop everything as close together in time as you can >(one drop is best of course, but sometimes it doesn't work that way), >and use the same log message for all files related to a particular >change. > >Derrick > > > > >------------------------------------------------------- >Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara >The only event dedicated to issues related to Linux enterprise solutions >www.enterpriselinuxforum.com > >_______________________________________________ >Htmlparser-developer mailing list >Htm...@li... >https://lists.sourceforge.net/lists/listinfo/htmlparser-developer > > > > |