[
https://issues.apache.org/jira/browse/CLEREZZA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998912#comment-12998912
]
Reto Bachmann-Gmür commented on CLEREZZA-435:
---------------------------------------------
For some reason wildcard import are not discouraged in scala, when using a poor
ide (or no ide) it is however handy to see for every class where it comes from.
Don't see why other indentation rules should apply for scala, xml or in xml in
scala, I see no reason to change the current practice of using exclusively tabs
for indentation.
> Coding convention compliance
> ----------------------------
>
> Key: CLEREZZA-435
> URL: https://issues.apache.org/jira/browse/CLEREZZA-435
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Hasan
> Priority: Trivial
> Attachments: zz-coding-conventions.v1.txt
>
>
> This issue is about writing code which should comply to certain conventions
> within Clerezza's committer.
> An initial document on the coding conventions is attached to this issue.
> If you want to update Clerezza code so that it complies with these
> conventions, please use this issue number
> when you commit your changes. We might do this every now and then, therefore,
> please don't resolve and close this issue.
> Please DON'T use this issue number in your commit, if you also have other
> changes in the code besides changes
> due to coding conventions. If you could separate your commit in two steps,
> then it would be the best.
> One for the coding conventions (using this issue number in your commit) and
> the other for the fix due to the "real" issue
> you want to solve (using the respective issue number).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
