commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Colebourne" <scolebou...@btopenworld.com>
Subject Re: [general] checkstyle report
Date Sat, 19 Oct 2002 23:01:55 GMT
I would certainly support setting these two things at the commons level. But
beyond that I would reckon that sticking with the checkstyle defaults is
about right. Over time, I reckon the projects will slowly fall into line.

Stephen

----- Original Message -----
From: "John Keyes" <jbjk@mac.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Sent: Saturday, October 19, 2002 11:54 PM
Subject: Re: [general] checkstyle report


> I know about how to fix these but what I was asking was
> was a more general topic.  As a good deal of the commons
> projects inherit the POM from the CVS root I was wondering
> if it would be a good idea to have a the checkstyle properties
> set at this level also so all of the 'mavenized' projects pick
> up the same settings.
>
> I think this mail is perhaps a bit more coherent ;)
>
> -John K
>
> On Saturday, Oct 19, 2002, at 23:47 Europe/Dublin, Stephen Colebourne
> wrote:
>
> > On lang, changing the line length to 120 helped a lot. Also, I don't
> > know if
> > maven is on checkstyle 2.4, but if so it has a setting to deal with
> > RuntimeException throws clauses in javadoc correctly which should be
> > set
> >
> > Stephen
> >
> > ----- Original Message -----
> > From: "John Keyes" <jbjk@mac.com>
> > To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
> > Sent: Saturday, October 19, 2002 11:29 PM
> > Subject: Re: [general] checkstyle report
> >
> >
> >> Yeap I'm on about the maven checkstyle report.
> >> -John K
> >>
> >> On Saturday, Oct 19, 2002, at 23:24 Europe/Dublin, Stephen Colebourne
> >> wrote:
> >>
> >>> Are you talking about the maven checkstyle report? Or a specific
> >>> projects?
> >>> Stephen
> >>>
> >>> ----- Original Message -----
> >>> From: "John Keyes" <jbjk@mac.com>
> >>>> I would be interested to hear people's opinions on the resolution
> >>>> of checkstyle's error reporting.  There are two options, one is to
> >>>> correct the code style so it conforms to the checkstyle settings,
> >>>> the other is to modify the settings to be less stringent.
> >>>>
> >>>> IMO, it would be great to have a common style across commons.
> >>>> I do think there would be opposition if this became a requirement
> >>>> though so I think relaxing the checkstyle properties is probably
> >>>> the way to go.
> >>>>
> >>>> What do others think?
> >>>>
> >>>> -John K
> >>>>
> >>>>
> >>>> --
> >>>> To unsubscribe, e-mail:
> >>> <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> >>>> For additional commands, e-mail:
> >>> <mailto:commons-dev-help@jakarta.apache.org>
> >>>>
> >>>
> >>>
> >>> --
> >>> To unsubscribe, e-mail:
> >>> <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> >>> For additional commands, e-mail:
> >>> <mailto:commons-dev-help@jakarta.apache.org>
> >>>
> >>
> >>
> >> --
> >> To unsubscribe, e-mail:
> > <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> >> For additional commands, e-mail:
> > <mailto:commons-dev-help@jakarta.apache.org>
> >>
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> > <mailto:commons-dev-help@jakarta.apache.org>
> >
>
>
> --
> To unsubscribe, e-mail:
<mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:commons-dev-help@jakarta.apache.org>
>


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


Mime
View raw message