Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 081209468 for ; Tue, 17 Jan 2012 13:36:28 +0000 (UTC) Received: (qmail 75385 invoked by uid 500); 17 Jan 2012 13:36:28 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 75338 invoked by uid 500); 17 Jan 2012 13:36:28 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 75330 invoked by uid 99); 17 Jan 2012 13:36:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jan 2012 13:36:28 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com designates 209.85.215.45 as permitted sender) Received: from [209.85.215.45] (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jan 2012 13:36:22 +0000 Received: by lags15 with SMTP id s15so2687199lag.32 for ; Tue, 17 Jan 2012 05:36:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=8eC7GL2KuDlnUNd7j7WRUsoguOcBwijzF4fokjVvYcs=; b=C9aITPr0SO78B/NSxVDZo1f2jPqfaMYeuIamxPjgZx+i5GB2vwCLJcI3Ze9rjy7GhK ToiHqh5oHlYu4CbqfvPoIYAuQHfsSK/RtO4zKgVtLj+MTuEgHOYWIevW7mKOkTZnFgmz R039oW3PYV13uIG9g7C4bYR5ziTLJorDd57Mc= Received: by 10.112.86.67 with SMTP id n3mr4078512lbz.29.1326807361668; Tue, 17 Jan 2012 05:36:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.95.141 with HTTP; Tue, 17 Jan 2012 05:35:40 -0800 (PST) From: Claus Ibsen Date: Tue, 17 Jan 2012 14:35:40 +0100 Message-ID: Subject: [FEEDBACK] - Upgrading to commons net 3.0 from 2.2 in camel-ftp, any foreseeable problems? To: dev Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi We have ticket https://issues.apache.org/jira/browse/CAMEL-4866 Does anyone see a problem if we upgrade commons net on trunk (eg Camel 2.10)? The reason being a bit careful is that its a major new release, and there is so many oddities with FTP transfer that can cause new problems for some, and fix previous problems for others etc. So usually some extra testing is a good idea for people using FTP transfer. So if anyone have tried using Commons Net 3.0 with camel-ftp on their test system or even production, then feedback is appreciated. We will most likely upgrade anyway, but in case someone shout that Commons Net 3.0 is buggy, then we can keep our fingers from the keyboard. -- Claus Ibsen ----------------- FuseSource Email: cibsen@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/