[
https://issues.apache.org/jira/browse/MAHOUT-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Anil updated MAHOUT-233:
------------------------------
Attachment: Eclipse-Codestyle.diff
Eclipse-Mahout-Codestyle.xml
I am attaching a slightly modified Lucene Code style the diff is also attached.
Using this i created almost zero check style errors from eclipse,
except a small violation i.e. empty constructor there is no space between {}
* the line length is set as 80 for wrapping. But checkstyle allows for lines
upto 120.
This is ok considering few unwrappable lines do need 120 chars like simple
map<map<map<>>>> declaration
Other than than it agrees with checkstyle perfectly. If the code in the mahout
bayes patch looks ok and if the eclipse code style looks ok, I will go ahead
and do a mass CTRL+SHIFT+F :)
> Modifying Mahout Check style to match our current coding style
> --------------------------------------------------------------
>
> Key: MAHOUT-233
> URL: https://issues.apache.org/jira/browse/MAHOUT-233
> Project: Mahout
> Issue Type: Task
> Affects Versions: 0.3
> Reporter: Robin Anil
> Fix For: 0.3
>
> Attachments: checkstyle-xml.patch, Eclipse-Codestyle.diff,
> Eclipse-Mahout-Codestyle.xml
>
>
> Checkstyle currently throws a lot of errors for small things like
> private static Logger log
> if(booleanVar == false) // Required for readability
> This task is created to track
> how to match the checkstyle to relax certain rules and
> changes in code for the strict ones
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
