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

Difference between revisions of "OSEE/Developer Guidelines"

(Code Quality Tools)
(Code Quality Tools)
Line 24: Line 24:
 
# Restart Eclipse  
 
# Restart Eclipse  
  
Configuration:
+
=== Configuration ===
  
# Import the following preference file:
+
# Launch Eclipse and select Window->Preferences
 +
 
 +
# Find Bugs use '''default''' settings
 +
#
  
 
== Monitor OSEE Bugs using Mylyn ==
 
== Monitor OSEE Bugs using Mylyn ==

Revision as of 18:21, 24 July 2009

Setup

Code Quality Tools

Update your eclipse installation with the following tools:

Installation for Find Bugs, PMD, and Check Style:

  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

Installation for Eclipse EMMA:

  1. Download zip file from the following link Eclipse Emma Zip File
  2. Unzip downloaded file into your dropins folder
  3. Restart Eclipse

Configuration

  1. Launch Eclipse and select Window->Preferences
  1. Find Bugs use default settings

Monitor OSEE Bugs using Mylyn

Integrating OSEE and Bugzilla

Before Committing 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