...
Configure the Project for Eclipse
Configuring project paths
Once the project is checked out, there are some Eclipse specific tasks that need to be done since this isn't an Eclipse project by default.
- Back in the Java perspective, on the Navigator or Package Explorer view, right-click on the pentaho-reporting-classic-core project and select Properties
- Select the Java Build Path item
- On the Source tab:
- Highlight the pentaho-reporting-classic-core item and click the Remove button.
- Click the Add Folder button, check the pentaho-reporting-classic-core ? /source folder and click OK
- Set the Default output folder to pentaho-reporting-classic-core/bin (and un-check the Allow output folders for source folders option if it is selected)
Configuring the classpath and dependent libraries
| Note | ||
|---|---|---|
| ||
Due to a bug in SVN, which causes binary checkins to corrupt the repository, the Reporting Projects do not always contain the latest versions of the internal libraries. The JARs checked in always represent the last release, not the latest development version. If you develop for the trunk-version of the reporting engine, make sure that you check out all dependent projects from the Subversion Repository and use these sources for your development. All modern IDEs are capable to define dependencies between subprojects of the same workspace, and therefore, if you set up your IDE correctly, pre-built JARs are not needed. |
...
At this point, the pentaho-reporting-classic-core project should compile and be ready for development.
You can repeat the same steps to work on the pentaho-reporting-classic-extensions project or any of the associated libraries (located under trunk/libraries):
...
| Include Page |
|---|
...
|