The last time I tried, the Mahout code has many instances of some phenomenon that checkstyle rejected, and there was no option in checkstyle to make them get along. If it hadn't been for that, I would have continued with the series of patches to run checkstyle from the maven builds and auto-configure eclipse.
On Tue, Dec 15, 2009 at 1:57 PM, Sean Owen <[email protected]> wrote: > I prefer #1 and am happy to apply this formatting across the board. It > seems more standard (though I don't know that even I have adhered to > it 100%) and is apparently our style. > > On Tue, Dec 15, 2009 at 6:50 PM, Robin Anil <[email protected]> wrote: >> In the new lucene codestyle this format is being used. >> >> Map<String,Element> map = new HashMap<String,Element>(); >> >> Where all our code has been using >> >> Map<String, Element> map = new HashMap<String, Element>(); >> >> Notice the space after , >> >> So i guess there is still some inconsistency in the style file >> >
