Spring IDE Development

Interested in following Spring Framework development?

Subscribe to the Spring IDE developer MailingList. You don't need to subscribe to the list just to submit a patch or two, but if you want to be involved with Spring development on a regular basis, consider subscribing.

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

Create a ticket in the Spring IDE's Trac Ticket System.

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

Trac Ticket System usage guidelines

Before creating a ticket, please:

  • Do your due-diligence to verify the bug does in fact exist.
  • Search the Jira to verify there is no existing issue reporting the bug you've found.
  • Consider tracking down the bug yourself in the Spring IDE codebase, and submitting a patch along with your bug report. This is a great time saver for the Spring IDE 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 IDE releases.

Looking for the Source Code?

The source code for the Spring IDE project is available through our Subversion repository.

  • Use the folder trunk for the latest Spring IDE development stream.
  • Use the folder tags for the previous Spring releases.

The information on building Spring IDE from it's source code can be found here.

Code Conventions

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

See also: SpringideProject, SpringideRepository, SpringideBuild, SpringideAutomaticBuild