Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of garydgregory@gmail.com
 designates 209.85.214.54 as permitted sender)
References: 
 <CAPoyBqQX6WVUVSFmqxknwCiG=PXbsvpw3D2R78EGR5w=RudBwA@mail.gmail.com>
From: Gary Gregory <garydgregory@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: 
 <CAPoyBqQX6WVUVSFmqxknwCiG=PXbsvpw3D2R78EGR5w=RudBwA@mail.gmail.com>
Date: Wed, 9 Jan 2013 07:25:45 -0500
Message-ID: <3922661237479044344@unknownmsgid>
Subject: Re: ETA SvnPubSub site migration
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=UTF-8

IMO code coverage should be part of the standard documentation for a
component.  Looking at code coverage helps establish or shake my
confidence in a component. It should definitively be part of ones
development checklist, I like to have the best code coverage for any
new code that I check in.

Gary

On Jan 9, 2013, at 5:16, Olivier Lamy <olamy@apache.org> wrote:

> Hi Folks,
> I have started importing some content for sub projects (exec,
> collections). I will try to do more later.
>
> Where is the place to document that ?
>
> Note: currently some content is imported which could be removed (I
> think about cobertura for modules which use sonar).
>
> What is the status about moving cobertura to a dedicated profile in
> parent pom ?
> Can I move it to a reporting profile in parent pom ?
>
> Thanks,
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org