Return-Path: Delivered-To: apmail-maven-issues-archive@minotaur.apache.org Received: (qmail 20701 invoked from network); 9 Jun 2009 17:23:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Jun 2009 17:23:01 -0000 Received: (qmail 90521 invoked by uid 500); 9 Jun 2009 17:23:13 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 90466 invoked by uid 500); 9 Jun 2009 17:23:12 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 90456 invoked by uid 99); 9 Jun 2009 17:23:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jun 2009 17:23:12 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [63.246.2.115] (HELO codehaus01.managed.contegix.com) (63.246.2.115) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jun 2009 17:23:03 +0000 Received: from codehaus01.managed.contegix.com (localhost.localdomain [127.0.0.1]) by codehaus01.managed.contegix.com (Postfix) with ESMTP id 087C414A81A1 for ; Tue, 9 Jun 2009 12:22:42 -0500 (CDT) Message-ID: <6617702.148491244568162009.JavaMail.haus-jira@codehaus01.managed.contegix.com> Date: Tue, 9 Jun 2009 12:22:42 -0500 (CDT) From: "Benjamin Bentmann (JIRA)" To: issues@maven.apache.org Subject: [jira] Commented: (MDEPLOY-104) Progress information is not suitable for logging In-Reply-To: <567619.148361244565882078.JavaMail.haus-jira@codehaus01.managed.contegix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 4e90ceb663894a42f12c0e28abbab431 X-Virus-Checked: Checked by ClamAV on apache.org [ http://jira.codehaus.org/browse/MDEPLOY-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179803#action_179803 ] Benjamin Bentmann commented on MDEPLOY-104: ------------------------------------------- What you want is already possible, simply run Maven in batch mode by adding {{-B}} to the CLI. The blog entry [Maven Continuous Integration Best Practices|http://www.sonatype.com/people/2009/01/maven-continuous-integration-best-practices/] provides further tips. > Progress information is not suitable for logging > ------------------------------------------------ > > Key: MDEPLOY-104 > URL: http://jira.codehaus.org/browse/MDEPLOY-104 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug > Components: deploy:deploy > Affects Versions: 2.4 > Environment: Hudson CI server > Reporter: Oleg Alexeyev > > In our project quite big files are deployed using maven-deploy-plugin (some are ~100 MB). During deploy phrase progress information is written to the standard output, on every 4KB, so the build log in Hudson is full of lines like this: > ... > 42376/86548K > 42380/86548K > 42384/86548K > 42388/86548K > 42392/86548K > 42396/86548K > 42400/86548K > ... > which makes it hard to find needed information in the log. > It would be nice if it would be configurable somehow at least, e.g. to disable printing the progress info. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira