2013/1/10 Gilles Sadowski :
> On Wed, Jan 09, 2013 at 09:23:26PM +0100, Olivier Lamy wrote:
>> 2013/1/9 Gilles Sadowski :
>> > On Wed, Jan 09, 2013 at 04:46:43PM +0100, Olivier Lamy wrote:
>> >> 2013/1/9 Olivier Lamy :
>> >> > 2013/1/9 Gilles Sadowski :
>> >> >> Hi.
>> >> >>
>> >> >>> >> [...]
>> >
On Wed, Jan 09, 2013 at 09:23:26PM +0100, Olivier Lamy wrote:
> 2013/1/9 Gilles Sadowski :
> > On Wed, Jan 09, 2013 at 04:46:43PM +0100, Olivier Lamy wrote:
> >> 2013/1/9 Olivier Lamy :
> >> > 2013/1/9 Gilles Sadowski :
> >> >> Hi.
> >> >>
> >> >>> >> [...]
> >> >>> >> > Note: currently some conten
2013/1/9 Gilles Sadowski :
> On Wed, Jan 09, 2013 at 04:46:43PM +0100, Olivier Lamy wrote:
>> 2013/1/9 Olivier Lamy :
>> > 2013/1/9 Gilles Sadowski :
>> >> Hi.
>> >>
>> >>> >> [...]
>> >>> >> > Note: currently some content is imported which could be removed (I
>> >>> >> > think about cobertura for
On Wed, Jan 09, 2013 at 04:46:43PM +0100, Olivier Lamy wrote:
> 2013/1/9 Olivier Lamy :
> > 2013/1/9 Gilles Sadowski :
> >> Hi.
> >>
> >>> >> [...]
> >>> >> > Note: currently some content is imported which could be removed (I
> >>> >> > think about cobertura for modules which use sonar).
> >>> >> >
2013/1/9 Phil Steitz :
> On 1/9/13 7:14 AM, Olivier Lamy wrote:
>> What about having a reporting profile (enabled per default).
>> And using -DskipReports to not generated cobertura, findbugs etc..
>>
>> Perso I like this idea as currently when you want to test a typo fix
>> in a .apt or .xdoc it's
2013/1/9 Olivier Lamy :
> 2013/1/9 Gilles Sadowski :
>> Hi.
>>
>>> >> [...]
>>> >> > 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
On 1/9/13 7:14 AM, Olivier Lamy wrote:
> What about having a reporting profile (enabled per default).
> And using -DskipReports to not generated cobertura, findbugs etc..
>
> Perso I like this idea as currently when you want to test a typo fix
> in a .apt or .xdoc it's very long to generate the sit
What about having a reporting profile (enabled per default).
And using -DskipReports to not generated cobertura, findbugs etc..
Perso I like this idea as currently when you want to test a typo fix
in a .apt or .xdoc it's very long to generate the site only for a typo
fix in documentation.
2013/1/
2013/1/9 Gilles Sadowski :
> Hi.
>
>> >> [...]
>> >> > 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
On Wed, Jan 09, 2013 at 08:37:33AM -0500, Gary Gregory wrote:
> On Wed, Jan 9, 2013 at 8:11 AM, Gilles Sadowski <
> gil...@harfang.homelinux.org> wrote:
>
> > On Wed, Jan 09, 2013 at 07:25:45AM -0500, Gary Gregory wrote:
> > > IMO code coverage should be part of the standard documentation for a
>
Hi.
> >> [...]
> >> > 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 p
2013/1/9 Gary Gregory :
> On Wed, Jan 9, 2013 at 8:11 AM, Gilles Sadowski <
> gil...@harfang.homelinux.org> wrote:
>
>> On Wed, Jan 09, 2013 at 07:25:45AM -0500, Gary Gregory wrote:
>> > IMO code coverage should be part of the standard documentation for a
>> > component. Looking at code coverage h
On Wed, Jan 9, 2013 at 8:11 AM, Gilles Sadowski <
gil...@harfang.homelinux.org> wrote:
> On Wed, Jan 09, 2013 at 07:25:45AM -0500, Gary Gregory wrote:
> > IMO code coverage should be part of the standard documentation for a
> > component. Looking at code coverage helps establish or shake my
> > c
2013/1/9 Gilles Sadowski :
> On Wed, Jan 09, 2013 at 07:25:45AM -0500, Gary Gregory wrote:
>> 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
On Wed, Jan 09, 2013 at 07:25:45AM -0500, Gary Gregory wrote:
> 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
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.
Gar
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
17 matches
Mail list logo
