Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "OSEE/Developer Guidelines"

(Code Quality Tools)
(Code Quality Tools)
Line 7: Line 7:
 
[http://findbugs.sourceforge.net/ Find Bugs] - Used to perform static analysis on java code
 
[http://findbugs.sourceforge.net/ Find Bugs] - Used to perform static analysis on java code
  
To install, add the following link
+
To install, add the following update site [http://findbugs.cs.umd.edu/eclipse]
 +
 
 +
=== PMD ===
 +
 
 +
[http://pmd.sourceforge.net/ PMD] - Additional static analysis and code duplication checks
 +
 
 +
To install, add the following link [http://pmd.sourceforge.net/eclipse]
 +
Select Eclipse 3.0 entry
 +
 
 +
=== Check Style ===
 +
 
 +
To install, add the following link [http://eclipse-cs.sf.net/update/]
  
 
== Monitor OSEE Bugs using Mylyn ==
 
== Monitor OSEE Bugs using Mylyn ==

Revision as of 15:15, 23 July 2009

Setup

Code Quality Tools

Find Bugs

Find Bugs - Used to perform static analysis on java code

To install, add the following update site [1]

PMD

PMD - Additional static analysis and code duplication checks

To install, add the following link [2] Select Eclipse 3.0 entry

Check Style

To install, add the following link [3]

Monitor OSEE Bugs using Mylyn

Integrating OSEE and Bugzilla

Before Committing Any Code

  1. Synchronize and Update
  2. Run Code Quality Checks
  3. Ensure all the tests are green. (Tests projects can be identified by their '*.test' suffix. All tests have to be executed as plug-in unit tests.)
  4. Ensure the reference documentation is up to date (i.e. reflects your changes) (Documentation is maintained in project 'via the OSEE wiki').

Back to the top