[mylyn-reviews-dev] Coding guidelines for Mylyn

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[mylyn-reviews-dev] Coding guidelines for Mylyn

From: Jacques Bouthillier <lmcbout@xxxxxxxxx>
Date: Wed, 11 Jun 2014 11:32:07 -0400
Delivered-to: mylyn-reviews-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/mylyn-reviews-dev>
List-help: <mailto:mylyn-reviews-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/mylyn-reviews-dev>, <mailto:mylyn-reviews-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/mylyn-reviews-dev>, <mailto:mylyn-reviews-dev-request@eclipse.org?subject=unsubscribe>

Hi ,

I would like to know if there is a written document to follow for the coding rules styles and coding guidelines when modifying or adding code to any Mylyn project.

There is one that exist for eclipse project:

http://wiki.eclipse.org/Recommenders/CodingConventions#Names_representing_constants_.28final_variables.29_must_be_all_uppercase_using_underscore_to_separate_words

Is it the one to follow?

Thanks

Jacques

Follow-Ups:
- Re: [mylyn-reviews-dev] Coding guidelines for Mylyn
  - From: Sam Davis

Prev by Date: Re: [mylyn-reviews-dev] [mylyn-dev] MyLyn Gerrit Dashboard on the LUNA release
Next by Date: Re: [mylyn-reviews-dev] Coding guidelines for Mylyn
Previous by thread: [mylyn-reviews-dev] MyLyn Gerrit Dashboard on the LUNA release
Next by thread: Re: [mylyn-reviews-dev] Coding guidelines for Mylyn
Index(es):
- Date
- Thread

Breadcrumbs