Return-Path: X-Original-To: apmail-creadur-dev-archive@www.apache.org Delivered-To: apmail-creadur-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 EDA5511D60 for ; Thu, 11 Sep 2014 10:23:23 +0000 (UTC) Received: (qmail 60582 invoked by uid 500); 11 Sep 2014 10:23:23 -0000 Delivered-To: apmail-creadur-dev-archive@creadur.apache.org Received: (qmail 60533 invoked by uid 500); 11 Sep 2014 10:23:23 -0000 Mailing-List: contact dev-help@creadur.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@creadur.apache.org Delivered-To: mailing list dev@creadur.apache.org Received: (qmail 60516 invoked by uid 99); 11 Sep 2014 10:23:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Sep 2014 10:23:23 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [85.220.129.33] (HELO smtp2.goneo.de) (85.220.129.33) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Sep 2014 10:22:55 +0000 Received: from localhost (localhost [127.0.0.1]) by smtp2.goneo.de (Postfix) with ESMTP id 1072023F348 for ; Thu, 11 Sep 2014 12:22:55 +0200 (CEST) X-Virus-Scanned: by goneo X-Spam-Score: -2.815 X-Spam-Level: Received: from smtp2.goneo.de ([127.0.0.1]) by localhost (smtp2.goneo.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29_ohoW8VUyV for ; Thu, 11 Sep 2014 12:22:54 +0200 (CEST) Received: from webmail.goneo.de (webmail.goneo.de [82.100.220.15]) by smtp2.goneo.de (Postfix) with ESMTPSA id 01CB123F3A1 for ; Thu, 11 Sep 2014 12:22:53 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 11 Sep 2014 12:22:53 +0200 From: "P. Ottlinger" To: dev@creadur.apache.org Subject: Re: [jira] [Created] (RAT-173) skip property does not skip report Reply-To: pottlinger@apache.org Mail-Reply-To: pottlinger@apache.org In-Reply-To: References: Message-ID: <385040599740c9c172af496f4f2a0fd6@aiki-it.de> X-Sender: pottlinger@aiki-it.de User-Agent: Goneo Webmail X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Flag: NO X-Old-Spam-Status: No, score=-2.815 tagged_above=-999 tests=[ALL_TRUSTED=-1, AWL=0.085, BAYES_00=-1.9] autolearn=ham Hi guys, does anyone of you see the use case of blocking the reports? On 2014-09-10 23:11, Chris Burroughs (JIRA) wrote: > Chris Burroughs created RAT-173: > ----------------------------------- > > Summary: skip property does not skip report > Key: RAT-173 > URL: https://issues.apache.org/jira/browse/RAT-173 > Project: Apache Rat > Issue Type: Bug > Components: maven > Affects Versions: 0.11 > Reporter: Chris Burroughs > > > The skip property added in RAT-164 skips `check` but not `report`. I understood RAT-164 to be okay for technical builds, but I do not really see a point in not having the report written during a site:site run? Why would I want to use RAT if I skip it completely? Thanks for your opinions, Phil