RE: [net][patch] jdk 1.4 specific call in VMSFTPEntryParser.java

2003-08-05 Thread Jeff Barrett
sorry. this patch passes the unit test: Index: src/java/org/apache/commons/net/ftp/parser/VMSFTPEntryParser.java === RCS file: /home/cvspublic/jakarta-commons/net/src/java/org/apache/commons/net/ftp/parser/VMSFTPEntryParser.java,v r

cvs commit: jakarta-commons/lang/src/java/org/apache/commons/lang/time DateFormatUtils.java

2003-08-05 Thread ggregory
ggregory2003/08/05 19:48:23 Modified:lang/src/java/org/apache/commons/lang/time DateFormatUtils.java Log: Oops, tiny typo: "time zone ." -> "time zone." Revision ChangesPath 1.5 +15 -15 jakarta-commons/lang/src/java/org/apache/commons/lan

Re: [LANG] Do we have a safeToString() ?

2003-08-05 Thread Henning P. Schmiedehausen
[EMAIL PROTECTED] writes: >StringUtils.defaultString() Takes a String, not an Object. >ObjectUtils.toString() What? This might return [EMAIL PROTECTED] in my memory. I want to call toString() on arbitrary objects and avoid the NPE when I do .toString(). Regards Hennin

RE: [lang] Recent changes cause Javadoc warnings

2003-08-05 Thread Steven Caswell
I missed that one in your earlier e-mail (I was too embarrassed looking at the DateUtils problems that I caused :) Should be a quick fix. BTW, Javadoc in 1.4.2 must be more picky than in 1.4.1, which I am running. When I ran the javadoc to test the DateUtils fixes a little while ago, it did not c

cvs commit: jakarta-commons/lang/src/test/org/apache/commons/lang/time DateUtilsTest.java

2003-08-05 Thread stevencaswell
stevencaswell2003/08/05 17:42:56 Modified:lang/src/test/org/apache/commons/lang/time DateUtilsTest.java Log: corrected the test of parseCVS with "h:mm z" format by replacing the current date/time with a series of calls using hard-coded time values Revisi

Re: [lang] Enum/JDK1.2 (was Work outstanding)

2003-08-05 Thread Henri Yandell
Seems to work :) Am back from the weekend away, will try to grokk from the emails etc what's left. Hen On Tue, 5 Aug 2003, Stephen Colebourne wrote: > OK, solution checked in now for the JDK1.2 Enum problem. It should all be OK > now. > > It should also be backwards compatable, and maybe offer