One thing I just saw on the Maven developer [1] section that I was
thinking might be useful (in Lucene as well) is to have downloadable
codestyle templates for IntelliJ and Eclipse defined and linked to
from the developer section of the website (or it could even be
checked out w/ the code). I have a Lucene one for IntelliJ that I
use, but I am not sure it captures our style 100%, but I would be
willing to post it and others can fix it up.
Granted, it doesn't completely solve the problem as people still need
to know it is there and use it, but at least it puts out a concrete
example of what the code style should be and one could do a friendly
nag every now and then for people to use it.
Just a thought,
Grant
[1] See further down on http://maven.apache.org/guides/development/
guide-m2-development.html
On May 17, 2007, at 2:56 PM, Otis Gospodnetic wrote:
Hi,
----- Original Message ----
From: Chris Hostetter <[EMAIL PROTECTED]>
I'd certianly prefer if all new code and new changes met teh style
guidelines we have setup -- tidying up the lines that are being
changed
anyway as part of the commit, but frankly i'd just as soon leave
code that
works but isn't super pretty well enough alone.
OG: That would be ideal. However, sometimes you want to work on
the existing code and the hard-to-parse style makes it harder for
you to follow and understand the code. I'm facing that now with
SolrIndexSearcher, which is what promoted this thread.
Otis
