Think you've found a bug or want to propose an enhancement?

Enter an issue in the Spring JIRA Issue Tracker.

We value your support there.  We can't fix bugs we don't know about!

JIRA usage guidelines

Before submitting an issue, please:

• Do your due-diligence to verify the bug does in fact exist.
• Search the issue tracker to verify there is no existing issue reporting the bug you've found.
• Consider tracking down the bug yourself in the Spring codebase, and submitting a patch along with your bug report. This is a great time saver for the Spring developers, and helps ensure the bug will be fixed very quickly.

Enhancement requests for new features are also welcome. The more concrete and rationale the request is, the greater the chance it will incorporated into future Spring releases.

Looking for the Source Code?

The source code for the core Spring project is available through anonymous CVS at SourceForge's CVS Server.

• Use CVS HEAD for the current Spring 2.x development stream.

• Use the CVS branch named "mbranch-1-2" for the Spring 1.2.x maintenance stream.

The source code for the Spring Portfolio products Spring Batch, Spring Web Flow, Spring Web Services, Spring-LDAP, and Spring-OSGi is available through anonymous SVN at SourceForge's Subversion Server.

Code conventions

To ensure consistency, code checked into a Spring project follows certain formatting conventions.  An Eclipse IDE code formatter profile for Spring is available below. This may be imported into your Eclipse instance.

• http://static.springframework.org/spring/xml/spring-code-conventions.xml