Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

  • In Eclipse, open the SVN Repositories Window (Window Menu ? > Show View ? > Other ? > SVN ? > SVN Repository)


  • Right click in the SVN Repository window ? > New ? > Repository Location...


  • Fill in the following fields:

    Field Name

    Value

    URL

    svn://source.pentaho.org/pentaho-reporting



  • The connection should be established and displayed in the SVN Repository window
    |

Check Out the Latest Code

...

  • In the SVN Repository windows, navigate to trunk ? engines ? > classic ? > core > trunk
  • Right-click and select Checkout...

  • Click on the Finish button...
  • From the New Project window, select Java Project...

  • In the New Java Project window, enter the Project Name (something like pentaho-reporting-classic-core) and click on the Next button...

  • In the Default output folder, append a /bin to the default folder and click Finish...

  • Ignore the warning message about resources that exist in the project...
  • At this point, the latest version of the project is checked out and the source code is sitting on your computer

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
titleBe Careful

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.

  • On the Libraries tab, click the Add JARs... button
    • Navigate to the pentaho-reporting-classic-core ? lib directory
    • Highlight all the jar files in that directory
    • Click on the OK button

  • Click on the OK button of the Properties dialog

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

...

ClassicDependencies
ClassicDependencies