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.
Difference between revisions of "OSEE/Developer Guidelines"
< OSEE
(→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.cs.umd.edu/eclipse Find Bugs Update Site] | * [http://findbugs.sourceforge.net/ Find Bugs] - Used to perform static analysis on java code - [http://findbugs.cs.umd.edu/eclipse Find Bugs Update Site] | ||
* [http://pmd.sourceforge.net/ PMD] - Additional static analysis and code duplication checks - [http://pmd.sourceforge.net/eclipse PMD Update Site] | * [http://pmd.sourceforge.net/ PMD] - Additional static analysis and code duplication checks - [http://pmd.sourceforge.net/eclipse PMD Update Site] | ||
− | * [http://eclipse-cs.sf.net Check Style] - Code Style Checks - [http://eclipse-cs.sf.net/update | + | * [http://eclipse-cs.sf.net Check Style] - Code Style Checks - [http://eclipse-cs.sf.net/update Check Style Update Site] |
== Monitor OSEE Bugs using Mylyn == | == Monitor OSEE Bugs using Mylyn == |
Revision as of 15:52, 23 July 2009
Contents
Setup
Code Quality Tools
Update your eclipse installation with the following tools:
- Find Bugs - Used to perform static analysis on java code - Find Bugs Update Site
- PMD - Additional static analysis and code duplication checks - PMD Update Site
- Check Style - Code Style Checks - Check Style Update Site
Monitor OSEE Bugs using Mylyn
Before Committing Any Code
- Synchronize and Update
- Run Code Quality Checks
- 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.)
- Ensure the reference documentation is up to date (i.e. reflects your changes) (Documentation is maintained in project 'via the OSEE wiki').