commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <tcu...@vafer.org>
Subject Re: [ALL] Commons Parent reports
Date Tue, 13 Mar 2012 14:36:02 GMT
> I didn't think we disagreed on refusing to spend a lot of time of correcting formatting
mess.

Not on that one :)

I just argue that in the days of code formatters "lot of time" has
become is quite significant.

>> Then you are probably a vocal minority here.
>
> Because I don't use an IDE or because I like clean code?

I hope that's a rhetorical question. I would think most java people use an IDE.

>> As long as there is someone that can run a code formatter before a
>> release that does not matter though.
>
> But would you be against running a formatter before committing the code.

It would be nice - but I would not want to require it.

>>  Menu > "Format Source Code" > Done.
>
> ... if they don't perform the above, CheckStyle is there to remind them they
> forgot to do it.

Why not just run the formatter in the very moment you are annoyed?

>> And I say - better let's give people the tools and not just point at them.
>
> The tools are there, but you have to tell people that they _must_ use them.

Commons has already enough rules and process. As long as the releases
are have clean code I wouldn't be too anal about the commits in
between.

Summary: if you guys insist - add it ...as long as components are OK
to disable it.
I personally just don't find it useful. But I can live with the fact
that you disagree.

Now that was already 4 cents :)

cheers,
Torsten

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


Mime
View raw message