Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-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 5C41E9CF4 for ; Fri, 5 Oct 2012 21:23:40 +0000 (UTC) Received: (qmail 57633 invoked by uid 500); 5 Oct 2012 21:23:40 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 57585 invoked by uid 500); 5 Oct 2012 21:23:39 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 57576 invoked by uid 99); 5 Oct 2012 21:23:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2012 21:23:39 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ctubbsii@gmail.com designates 209.85.217.169 as permitted sender) Received: from [209.85.217.169] (HELO mail-lb0-f169.google.com) (209.85.217.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2012 21:23:33 +0000 Received: by mail-lb0-f169.google.com with SMTP id k6so1806054lbo.0 for ; Fri, 05 Oct 2012 14:23:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Mxrx93MnUtM93aJQm9hplTwJ5J63sJGZVxzkC29CVCc=; b=ffr3piu//8vrJYYEka86hnLljPsjODj4H62zHD8CTTkeiYmiVeUYIgoxU7I2qkehSz FIlqQ14ucPJ6zNLgHsSbibPhrRVKqDl086d2oHPQP8DdVp2MA7DqL/5Bm/NTe3uwH3Wh EmqiwcUMWGb4z64EyHwh572Xc8kQCJ/37SXJhdUdPPGoUSOgomGUMcTGa8ei02ZWguiZ n/Eem30X86taqkzRrlcfaGl3AEQpRwR9rxVS+T+E0rqiiXyrPWnKhwLf2nrQaGv4yJNr ok1MmjpCYwLxUBJirNUZjzbvh/wYBVeGjBMbfnE43ngcOcsbvpJbcus6Q6FdKq0gvAa/ CRfg== MIME-Version: 1.0 Received: by 10.152.104.107 with SMTP id gd11mr7293324lab.25.1349472192445; Fri, 05 Oct 2012 14:23:12 -0700 (PDT) Received: by 10.114.63.242 with HTTP; Fri, 5 Oct 2012 14:23:12 -0700 (PDT) In-Reply-To: References: Date: Fri, 5 Oct 2012 17:23:12 -0400 Message-ID: Subject: Re: builds failing From: Christopher Tubbs To: dev@accumulo.apache.org Content-Type: text/plain; charset=ISO-8859-1 I'm not sure which reports we need or don't need, but the following has an example of how to do it in the build section, if we need to. The main take-away is to attach it to the "pre-site" phase, so it doesn't occur during the default build lifecycle. There's also another suggestion farther down to add it to the maven-site-plugin configuration. I'm not sure I like that solution as much, but it may work also, and has the advantage of keeping the reporting plugins separated from the main build. http://stackoverflow.com/questions/6931360/what-is-the-proper-way-to-use-cobertura-with-maven-3-0-2 On Thu, Oct 4, 2012 at 12:09 PM, Billie Rinaldi wrote: > It looks like builds started failing after the Ubuntu build servers were > upgraded recently. They're failing because they can't find the cobertura > xml output to publish. There is some evidence that the combination of > maven and cobertura-maven-plugin we're using won't generate xml output for > cobertura unless the cobertura plugin is in the builds section of the pom > rather than the reporting section of the pom. > > http://stackoverflow.com/questions/9398662/maven-cobertura-plugin-not-generating-coverage-xml > > I can replicate this locally by running mvn clean cobertura:cobertura. The > coverage.xml files are not there. So I'm not sure why this was working > until now. Does anyone see a problem with moving the cobertura plugin to > the builds section of the pom? Do we still want both the xml and html > output to be generated? > > Billie