Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 04116200D12 for ; Sat, 7 Oct 2017 21:35:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 026F8160BDC; Sat, 7 Oct 2017 19:35:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 479811609DA for ; Sat, 7 Oct 2017 21:35:05 +0200 (CEST) Received: (qmail 82623 invoked by uid 500); 7 Oct 2017 19:35:04 -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 82612 invoked by uid 99); 7 Oct 2017 19:35:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Oct 2017 19:35:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B3834CA2E4 for ; Sat, 7 Oct 2017 19:35:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id bxGkRnNHfckS for ; Sat, 7 Oct 2017 19:35:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 22BE95FD71 for ; Sat, 7 Oct 2017 19:35:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 638A3E0EFA for ; Sat, 7 Oct 2017 19:35:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id AA8872435E for ; Sat, 7 Oct 2017 19:35:00 +0000 (UTC) Date: Sat, 7 Oct 2017 19:35:00 +0000 (UTC) From: "Andreas Dangel (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (MPMD-246) Output details of processing errors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 07 Oct 2017 19:35:06 -0000 Andreas Dangel created MPMD-246: ----------------------------------- Summary: Output details of processing errors Key: MPMD-246 URL: https://issues.apache.org/jira/browse/MPMD-246 Project: Maven PMD Plugin Issue Type: Improvement Components: PMD Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.9 To help debugging processing errors (or any error in PMD), maven should be able to output the processing errors with exception stacktraces. Currently, only the number of the problematic files are displayed. Furthermore, PMD usually adds the processing errors to the XML report. But the XML report that is generated with the maven pmd plugin doesn't contain the errors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)