Classic Reporting Engine and SDK

The Pentaho Classic Reporting Engine is a embeddable Java reporting library that is used by the report designer to generate reports. The library can be used in both in server-side and client side scenarios. Originally known as JFreeReport, it is designed to follow the approach of banded reporting with absolutely positioned elements.

The SDK is a packaging of the Classic Engine, documentation and and all of the supporting libraries required to embed the Pentaho Reporting Engine into your application.

Recent News and Releases
- 2010-06-14 Stable builds of Pentaho reporting 3.6.1 released. more info.
- 2010-06-14 Pentaho Report Engine Classic 3.6.1-stable: download now.
- 2010-06-14 Pentaho Report Engine SDK 3.6.1-stable: download now.
- 2010-06-14 Pentaho Report Libraries updated 1.1.7 and 1.1.8: download now.
Stable
Classic Reporting Engine 3.6.1 stable
This is a bug fix release and supports BI Platform 3.6.
- Downloads - Source - Documentation - Forum  

Reporting Engine SDK 3.6.1 stable
This is a bug fix release and supports BI Platform 3.6.
- Downloads - Source - Documentation - Forum  

Release Notes for 3.6.1
In Development
Developer Resources
- Roadmap - Open Issues - Continuous Integration Builds  
- Source - Documentation - Developer Forum  
Reporting Engine 3.6.2 - In Progress
This will be a point release with critical bug fixes only.
- Task Board for 3.6.2 - JIRA Cases for 3.6.2 - Source (3.6 trunk)  
Reporting Engine 3.7.0 - In Progress
This will be a minor release with bug fixes and some new features.
- Task Board for 3.7 - JIRA Cases for 3.7 - Source (trunk)  
Quick Links
Reporting Sub-Projects
You may also be interested in contributing to one or more of these Pentaho Reporting related projects:
Pentaho Advertisement
Contribute to the Project
You can participate by contributing new code, reporting bugs, testing new releases, answering questions and more; Email us the proposed contribution and any other relevant details. Welcome to the team.

- Write a tech tip
- Report a bug in JIRA
- Answer posts on the forums
- Write some code
- How to Contribute