This Style guide is unofficial as of yet. Please see the Code Contribution Guidelines page for our old code style recommendations, which are still currently in effect. |
Per the Code Contribution Guidelines page (see "Coding Conventions" section), our existing style guide is listed as follows:
Your code needs to follow the Sun Java code conventions with the following minor modifications:
- Curly braces must be on new lines.
- Source files must have a copy of the copyright Duraspace notice and BSD license at the top (see Licensing of Contributions below). Also take a look at Copyright and Licensing.
- You must use 4-space tabulation.
- 'else' should be on a new line. 'else if' stays on one line.
- Users of the Eclipse IDE can have eclipse do the formatting automatically using this profile: - Dspace-eclipse-format.xml. See the Eclipse section below for details of how to apply this profile.
Your code should be well commented with Javadoc (including package and class overviews). All code contributions must come with Documentation. At a bare minimum, this should include Technical Documentation covering all configuration options and/or setup. See Documentation Contributions below for more details.
These existing style guidelines are based heavily on the Sun coding conventions (circa 1999) which are no longer maintained, but still available at http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html
Because the Sun Java style guide is no longer maintained, it will not be keeping up with current Java style best practices, features, etc. We should consider whether we continue to base our style off this outdated guide, use a more modern guide, or develop our own guide.
If you would like to comment on this proposal, please add your thoughts to this Pull Request: https://github.com/DSpace/DSpace/pull/1895 |
Bolded rules are a change from our current Style Guide.
K&R style braces required. Braces required on all blocks.
if (code) { // code } else { // code } |
import java.util.*
). Duplicated or unused imports are also not allowed.@author
tags are optional, but should refer to an individual's name or handle (e.g. GitHub username) when includedMaximum length of lines is 120 characters.
Each source file must contain the required license header, e.g.
/** * The contents of this file are subject to the license and copyright * detailed in the LICENSE and NOTICE files at the root of the source * tree and available online at * * http://www.dspace.org/license/ */ |
The Google Java Style Guide is at https://google.github.io/styleguide/javaguide.html
Some of the primary differences of this style include:
The Fedora project has its own style guide at https://wiki.duraspace.org/display/FF/Code+Style+Guide
Some of the primary differences of this style include:
While not yet implemented, we likely would want to implement some verification of code style guidelines via Checkstyle. Checkstyle is widely used in the Java world, and supports both Google and Sun Java conventions, as well as custom configurations.
Which git branches would we want to enable Checkstyle on?
master
branch, and perhaps just specific modules (e.g. "dspace-spring-rest") on the master
branch.master
branch only may complicate cherry-picking of code changes from other branches (as line numbers, spacing, etc may change when the code is updated to use the latest DSpace Style Guide)Most major IDEs include plugins that support Checkstyle configurations. The plugin usually let you import an existing "checkstyle.xml" configuration to configure your IDE to use and/or validate against that style. (Please note: we have not tested all these plugins as of yet, so mileage may vary until we test/verify the plugin is usable)
checkstyle.xml
+
in the table). Select our checkstyle.xml
checkstyle.xml
Ctrl + Alt + L
) to reformat the open source file based on Checkstyle rules.import
statements use an asterisk, you will also need to do "Code -> Optimize Imports" (Ctrl + Alt + O
) to correct those.*.java, *.xml
" (As we'll only reformat Java and XML files)Finally, run Checkstyle against the module. There likely will still be a few failures to fix manually.
mvn install mvn -U checkstyle:check |