You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2013/11/11 17:53:22 UTC

[jira] [Resolved] (OAK-98) Source code formatting, code conventions, Javadocs

     [ https://issues.apache.org/jira/browse/OAK-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved OAK-98.
-----------------------

    Resolution: Fixed

afaik we agreed to follow a common coding style a long time a ago... not for everything but for some basic things.

> Source code formatting, code conventions, Javadocs
> --------------------------------------------------
>
>                 Key: OAK-98
>                 URL: https://issues.apache.org/jira/browse/OAK-98
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Thomas Mueller
>            Priority: Minor
>
> I would prefer if we use a somewhat unified coding style, for things like
> } else {
> versus
> }
> else {
> and so on. There are various style guides, for example:
> http://developers.sun.com/sunstudio/products/archive/whitepapers/java-style.pdf
> http://www.oracle.com/technetwork/java/codeconv-138413.html
> http://java.sun.com/docs/codeconv/CodeConventions.pdf



--
This message was sent by Atlassian JIRA
(v6.1#6144)