Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Coding Conventions

Revision as of 13:50, 30 July 2007 by David williams.acm.org (Talk | contribs) (Removed exact duplicate sentence. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=198236)

Sun has established coding standards that are generally considered reasonable, as evidenced by their widespread adoption by other Java-based development efforts (e.g., the Apache Jakarta project). One of the goals is to make the Eclipse Platform blend in with the Java 2 platform. This goal is furthered by our following suit.

Sun's Code Conventions for the Java Programming Language covers filenames, file organization, indentation, comments, declarations, statements, white space, naming conventions, and programming practices. All code written for the Eclipse Platform should follow these conventions except as noted below. We deviate only in places where our needs differ from Sun's; when we do deviate, we explain why. (The section numbers shown below are Sun's.)


  • Section 3.1.1 Beginning Comments

The Eclipse project has specific guidelines for copyright notices to appear at the beginning of source files. See the Eclipse Project Charter for details.

  • Section 9 Naming Conventions

The Eclipse project has more specific naming conventions. See Eclipse Project Naming Conventions for details.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.