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)
m (Code Quality Tools)
Line 15: Line 15:
 
# Drag the Update Site URLs into the '''Software Update and Add-ons''' dialog
 
# Drag the Update Site URLs into the '''Software Update and Add-ons''' dialog
 
# Select code style tools to install - '''for Find Bugs make sure you only select the Eclipse 3.4 or later entry'''
 
# Select code style tools to install - '''for Find Bugs make sure you only select the Eclipse 3.4 or later entry'''
# Click the '''Install'' button
+
# Click the '''Install''' button
 
# Once installation completes, restart eclipse
 
# Once installation completes, restart eclipse
  

Revision as of 17:18, 24 July 2009

Setup

Code Quality Tools

Update your eclipse installation with the following tools:

Installation:

  1. Launch Eclipse and go to Help->Software Updates->Available Software
  2. Drag the Update Site URLs into the Software Update and Add-ons dialog
  3. Select code style tools to install - for Find Bugs make sure you only select the Eclipse 3.4 or later entry
  4. Click the Install button
  5. Once installation completes, restart eclipse
  1. Import the following preference file:

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