Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 9332 invoked from network); 29 Dec 2003 22:27:59 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 29 Dec 2003 22:27:59 -0000 Received: (qmail 29780 invoked by uid 500); 29 Dec 2003 22:27:43 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 29719 invoked by uid 500); 29 Dec 2003 22:27:42 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 29706 invoked from network); 29 Dec 2003 22:27:42 -0000 Received: from unknown (HELO rwcrmhc13.comcast.net) (204.127.198.39) by daedalus.apache.org with SMTP; 29 Dec 2003 22:27:42 -0000 Received: from sleepingbear (c-24-14-39-135.client.comcast.net[24.14.39.135]) by comcast.net (rwcrmhc13) with SMTP id <2003122922274801500p1k2ge>; Mon, 29 Dec 2003 22:27:49 +0000 Content-Type: text/plain; charset="us-ascii" From: steve cohen To: "Jakarta Commons Developers List" Subject: [NET] VMSFTPEntryParser bug? Date: Mon, 29 Dec 2003 16:27:50 -0600 User-Agent: KMail/1.4.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200312291627.50731.scohen@javactivity.org> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I am trying to build commons-net prior to making some changes and some other issues have come to light. One of the tests is failing for me - VMSFTPEntryParserTest.testParseFileList(). This test seems poorly implemented, since the class being tested builds its list of files using a HashMap to eliminate dupes, I presume, and then spits out the list by calling values() on the HashMap - which spits out the values in an order that is different from the one the test is expecting. I was running this under java 1.3 on linux. I switched to java 1.4 and it is also failing but on a different line. I'm not sure what platform Jeff is on when he did the build, but I think I should rewrite this test in a way that doesn't assume any particular order since this seems to be JDK-implementation dependent. The JavaDoc for HashMap specifies no order that should be expected for HashMap.values(), nor for HashMap.keySet() for that matter. We could probably achieve a dependable order by using a TreeMap.keySet() instead. --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org