Mailing-List: contact commits-help@ace.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ace.apache.org
Date: Sat, 6 Jun 2015 15:46:08 +0000 (UTC)
From: "Marcel Offermans (JIRA)" <jira@apache.org>
To: commits@ace.apache.org
Message-ID: <JIRA.12767750.1421335270000.9889.1433605568112@Atlassian.JIRA>
In-Reply-To: <JIRA.12767750.1421335270000@Atlassian.JIRA>
References: <JIRA.12767750.1421335270000@Atlassian.JIRA>
 <JIRA.12767750.1421335270371@arcas>
Subject: [jira] [Resolved] (ACE-508) When rolling back the cause is not
 shown in the target's log
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Offermans resolved ACE-508.
----------------------------------
    Resolution: Fixed

Committed a solution for this.

> When rolling back the cause is not shown in the target's log
> ------------------------------------------------------------
>
>                 Key: ACE-508
>                 URL: https://issues.apache.org/jira/browse/ACE-508
>             Project: ACE
>          Issue Type: Improvement
>            Reporter: Alexander Broekhuis
>            Assignee: Marcel Offermans
>            Priority: Minor
>
> Currently the Log of a target will show that deployment of a package has failed, but it does not show a cause or reason of the failure.
> For resolving the problem, this is needed. 
> For example, if a ResourceProcessor fails with a ResourceProcessorException, that exception including the message could be added to the log.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)