Nuxeo Core Developer Guide

Coding and Design Guidelines

Updated: October 22, 2018 Page Information Edit on GitHub

Beside all the QA and CI tools providing code analysis and safety nets, the Nuxeo strategy about code quality relies on continuous improvement. It is not viable, nor wanted (for stability purpose), to update the whole code once or regularly regarding a specific subject. When editing a class, one must improve its quality in the mean time:

  • first, update the header and format the code,
  • then, clean up the code (dead parts, unused imports, potential NPE, field overwrite, deprecated usage, synchronize POM...),
  • finally, do the work for which you opened that class.

Keep in mind that quality development rule: don't increase the debt, reduce the debt.

This chapter lists some rules that must be strictly followed when contributing to Nuxeo source code.

2 months ago manonlumeau NXDOC-1650 fix about integrating changes, add mention on multiple attempts
2 years ago Manon Lumeau 9 | emove children display macr
3 years ago Julien Carsique 8
3 years ago Julien Carsique 7 | code quality continuous improvement
3 years ago Eric Barroca 6
7 years ago Julien Carsique 4
7 years ago Julien Carsique 5 | Migrated to Confluence 4.0
7 years ago Julien Carsique 3
7 years ago Florent Guillaume 2
8 years ago Stéfane Fermigier 1
History: Created by Stéfane Fermigier

We'd love to hear your thoughts!

All fields required