Issue 11 in constants-to-enum-eclipse-plugin: Adapt coding conventions from JDT

[codesite...@google.com]

Status: Accepted
Owner: b.muskalla
Labels: Type-Task Priority-Medium

New issue 11 by b.muskalla: Adapt coding conventions from JDT
http://code.google.com/p/constants-to-enum-eclipse-plugin/issues/detail?id=11

As in the end we'll likly be pretty close to JDT or even part of it, we
should adapt the coding conventions from Eclipse and especially from JDT.

See http://wiki.eclipse.org/index.php/Development_Conventions_and_Guidelines
and additional rules used in the JDT UI project:

instance variables start with an f prefix
non final static variables start with an fg prefix
we use the compact assignment form (a= b, i.e. no space on the left of
equals)

(taken from http://eclipse.org/jdt/ui/dev.php)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings