# Optional Checks

- About
- Checkstyle
- Documentation
- Release Notes
- Configuration
- Property Types
- Running
- Ant Task
- Command Line
- Available Checks
- Standard Checks
- Javadoc Comments
- Naming Conventions
- Headers
- Imports
- Size Violations
- Whitespace
- Modifiers
- Block Checks
- Coding
- Class Design
- Duplicate Code
- Metrics
- Miscellaneous
- Optional Checks
- Overview
- Configuration
- J2EE Checks
- Extending Checkstyle
- Writing checks
- Writing filters
- Writing listeners
- Javadoc
- SourceForge
- Mailing Lists
- Bug Database
- Feature Requests
- Developers
- Project Page
- CVS Repository
- Contributing

- Hosted by:

## Overview

Standard Checkstyle Checks are applicable to general Java coding style and require no external libraries. An optional Check is for special applications or requires additional libraries. There are are optional Checks for:

- J2EE Requirements

## Configuration

As with standard checks, optional checks are configured as submodules of TreeWalker. The shortened name of an optional Check module must include the appropriate package name prefix. For example, this is a configuration fragment for Check com.puppycrawl.tools.checkstyle.checks.j2ee.EntityBean:

    <module name="j2ee.EntityBean"/>

Consult the Checkstyle configuration manual to learn how to integrate optional Checks into the package configuration so that you can use fully shortened names such as UnusedLocalVariable.

Copyright © 2001-2005, Oliver Burn