Quick Search
  1. Dashboard
  2. > GeoTools Developers Guide
  3. > 5 Project Conventions

GeoTools

UserGuide

DeveloperGuide

  • .bookmarks
  • 1 Introduction
  • 2 Building
  • 3 Communication
  • 4 Roles and Responsibilities
  • 6 Documentation
  • 7 Project Procedures
  • 8 Design and Architecture
  • 9 Tools
  • A Reference
  • Home

wiki

News Operations
  • View
  • Attachments (0)
  • Info
Browse Space
  • Pages
  • News
  • Labels
  • Attachments
  • Bookmarks
  • Mail
  • Advanced
  • View a printable version of the current page.
  • Export Page as PDF
  • Log In
  • Sign Up
GeoTools Developers Guide

5 Project Conventions

Added by jgarnett, last edited by jgarnett on Nov 20, 2006  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.
  • 5.1 Coding Guidelines
    • 5.1.1 Coding Conventions — use Jalopy
    • 5.1.2 Do not return null
    • 5.1.3 Logging
    • 5.1.4 Exception handling
    • 5.1.5 Avoid assumptions
    • 5.1.6 Converting URLs to Files
    • 5.1.7 Use of Assertions, IllegalArgumentException and NPE
  • 5.2 Naming Conventions — use PMD
  • 5.3 Module Directory Structure
  • 5. 5 Refactoring
  • 5. 6 Code Profiling
  • 5. 7 Testing — JUnit
    • Online Test Fixtures
  • 5. 8 Test Data
  • 5. 9 Versioning

Children (8)

  Hide Children  |  View in Hierarchy
5.1 Coding Guidelines
5.2 Naming Conventions
5.3 Module Directory Structure
5. 5 Refactoring
5. 6 Code Profiling
5. 7 Testing
5. 8 Test Data
5. 9 Versioning

Powered by a free Atlassian Confluence Open Source Project License granted to The Codehaus. Evaluate Confluence today.

  • Powered by Atlassian Confluence 2.9.2, the Enterprise Wiki.
  • Bug/feature request –
  • Atlassian news –
  • Contact administrators