commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: ETA SvnPubSub site migration
Date Wed, 09 Jan 2013 12:25:45 GMT
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


Mime
View raw message