Page Operations
Browse Space
Eclipse has several different types of projects, and Pentaho utilizes the simple project and the Java project. Simple projects have the most basic Eclipse project configuration and capabilities, which encompasses little more than file browsing. Java projects contain source code that needs compiling and configuration files such as the .classpath file, which will set up the build libraries found in the \lib sub-directory of the source tree. The pentaho-data, pentaho-solutions and pentaho-preconfiguredinstall projects are all Eclipse simple projects. The pentaho project and the pentaho-standalone project are both Eclipse Java projects.
The recommended structure for the modules you are pulling from Subversion is to download them as sibling directories - this structure will accommodate the platform in finding your solutions directory automatically, and also make keeping track of the different modules a bit easier.
Immediately after checking out the pentaho project, you will notice (if your "Build Automatically" setting is active) that the project is being compiled. The project may compile with warnings, but not with compilation errors. Be patient, this task may take up to a minute, depending on the speed of your computer. The pentaho-standalone project will NOT compile automatically, because there are some setup steps that must be taken before this project can be run.
To complete the examples in this document, you will need to checkout the following projects:
- pentaho
- pentaho-data
- pentaho-solutions
- pentaho-preconfiguredinstall
- pentaho-standalone
Retrieving Different Codelines
At this point, you may want to retrieve the latest code for the platform, which is the codeline that is being built for our next release. Or, if you are investigating a problem with the latest production release, you will want version 1.2.x. The next two sections explain how to get one the 1.2 branch of the code, versus the latest, which is, by Subversion terminology, "the trunk".
Either way, to retrieve the source, simply issue a command to Subversion either from a command line or via your favorite Subversion client application. We've been using Subclipse.
Get the Latest Code
In the SVN Repository View, expand your repository connection. Earlier, we created svn://source.pentaho.org/svnroot.
- Expand a project. In this example, we will use pentaho.
- Right click trunk.
- From the right-click menu, select Checkout... The Checkout from SVN wizard loads.
- Follow the instructions in the wizard to checkout the project to your workspace. Name the new Eclipse project the same name that was used for the project in Subversion.
- Repeat these steps for each project listed above.
After you checkout the pentaho project, if it does not compile automatically, compile it manually from the Project menu. Select the pentaho project from the view on the left, then from Project menu, choose the 'Build Project' option. Only the pentaho project needs to be compiled, the rest of the projects are simple projects that do not need to be built.
If you do experience errors, take the necessary steps to resolve them before moving forward. The typical reason for compilation errors when setting the project up for the first time is either the module structure does not follow the recommended hierarchy, or a third party library is missing from the /lib directory or the .classpath file. If you're still stuck, we can help! Submit the compilation error that Eclipse is reporting to our forums at http://forums.pentaho.org
. Many community members and Pentaho developers are ready to help!
Get the Version 1.2.x Codeline
In the SVN Repository View, expand your repository connection. Earlier, we created svn://source.pentaho.org/svnroot.
- Expand a project. In this example, we will use pentaho.
- Expand the branches tree.
- Right click 1.2.
- From the right-click menu, select Checkout... The Checkout from SVN wizard loads.
- Follow the instructions in the wizard to checkout the project to your workspace. Name the new Eclipse project the same name that was used for the project in Subversion.
- Repeat these steps for each project listed above.
After you checkout the pentaho project, if it does not compile automatically, compile it manually from the Project menu. Select the pentaho project from the view on the left, then from Project menu, choose the 'Build Project' option. Only the pentaho project needs to be compiled, the rest of the projects are simple projects that do not need to be built.
If you do experience errors, take the necessary steps to resolve them before moving forward. The typical reason for compilation errors when setting the project up for the first time is either the module structure does not follow the recommended hierarchy, or a third party library is missing from the /lib directory or the .classpath file. If you're still stuck, we can help! Submit the compilation error that Eclipse is reporting to our forums at http://forums.pentaho.org. Many community members and Pentaho developers are ready to help!
Quick Links For This Document
