Return-Path: Delivered-To: apmail-maven-m2-dev-archive@www.apache.org Received: (qmail 8447 invoked from network); 7 Feb 2005 01:16:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 7 Feb 2005 01:16:57 -0000 Received: (qmail 94477 invoked by uid 500); 7 Feb 2005 01:16:56 -0000 Delivered-To: apmail-maven-m2-dev-archive@maven.apache.org Received: (qmail 94457 invoked by uid 500); 7 Feb 2005 01:16:56 -0000 Mailing-List: contact m2-dev-help@maven.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: List-Id: "Maven 2 Developers List" Reply-To: "Maven 2 Developers List" Delivered-To: mailing list m2-dev@maven.apache.org Received: (qmail 94443 invoked by uid 99); 7 Feb 2005 01:16:56 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from beaver.codehaus.org (HELO codehaus.org) (64.7.141.17) by apache.org (qpsmtpd/0.28) with SMTP; Sun, 06 Feb 2005 17:16:55 -0800 Received: (qmail 9339 invoked from network); 7 Feb 2005 01:30:12 -0000 Received: from localhost (HELO beaver.codehaus.org) (127.0.0.1) by codehaus.org with SMTP; 7 Feb 2005 01:30:12 -0000 Message-ID: <7326572.1107739812769.JavaMail.orion@beaver.codehaus.org> Date: Sun, 6 Feb 2005 20:30:12 -0500 (EST) From: jira@codehaus.org To: m2-dev@maven.apache.org Subject: [jira] Commented: (MNG-122) clean up of exception handling and error reporting In-Reply-To: <4062852.1107739700162.JavaMail.orion@beaver.codehaus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N The following comment has been added to this issue: Author: Brett Porter Created: Sun, 6 Feb 2005 8:28 PM Body: we also need to review how cleanup occurs in exceptional cases, as there seem to be some extra failuers (particularly in wagon) which could cause problems in an embedded environment. --------------------------------------------------------------------- View this comment: http://jira.codehaus.org/browse/MNG-122?page=comments#action_29611 --------------------------------------------------------------------- View the issue: http://jira.codehaus.org/browse/MNG-122 Here is an overview of the issue: --------------------------------------------------------------------- Key: MNG-122 Summary: clean up of exception handling and error reporting Type: Improvement Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: m2 Fix Fors: 1.0-alpha-1 Assignee: Reporter: Brett Porter Created: Sun, 6 Feb 2005 8:28 PM Updated: Sun, 6 Feb 2005 8:28 PM Description: we need to get rid of the traces for non-fatal errors, and give something user friendly. The traces for fatal errors need to be more descriptive. --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira