IntelliJ Checkout and Build Process

Skip to end of metadata
Go to start of metadata
This section is intended to help a new developer set up the project from within IntelliJ

Cloning forked repository

Once your project has been forked on github, you can use the included feature to “Checkout from Repository” under VCS with Git. This will clone the repository to your the desired location.

Importing Cloned Project

1. After you have cloned your git repository, you must import the project whence it was clone. Select the root to get all of the sub-projects / modules

2. Make sure to select "Import project from external model" and select "Eclipse"

3. The default project configuration is sufficient for this task.

4. Ensure that all Eclipse projects are selected to import as modules. 

5. Select JDK 6.

6. No frameworks should be detected. Click "Finish"

Building Modules

Here, we will set up the workspace for development purposes.


This section describes the setting of different warnings as to ensure that the baseline is free of these types of warnings. In IntelliJ, the setting is not called “warnings” but rather “inspections”.

  1. Go to “File >> Settings >> Inspections [under “Project Settings]
  2. Check the following and set them to the associated severity level
  • Imports
    • Unused import [warning]
  • Serialization issues
    • Serializable class without 'serialVersionUID' [warning]
  • Assignment issues
    • Assignment used as condition [warning]
  • Control flow issues
    • Fallthrough in 'switch' statement [warning]
  • Visibility issues
    • Method overrides package-local method of superclass located in other package [warning]

Making Modules

This will allow you to compile your separate modules to as to remove

If you attempt to make any module, you will be presented with the following screen with errors throughout the source.

Per module (except for assembly module, since there is no source for this project) you must perform the following steps.

1. Add the build.xml to the Ant Build window

2. Run the subfloor.resolve Ant Build target to download the necessary jars and other libraries (note: sometimes this may take a long time, please be patient). Once this is complete, you should see that the Ant build completed successfully.

3. Include “lib” directories in your module's configuration. This will allow the module to use the jars which were just downloaded from the previous step.

3.a Delete any previous project includes (except for java 1.6, module source, and jUnit if it is present)

3b. Include the following lib directories (lib, test-lib, codegen-lib, dev-lib) (note: not all projects have all 4 directories.) Do this by clicking the '+ >> Jars or directories'. Additionally, since the other modules are all present in the workspace, be careful not to select the lib directory from a different module. Hit “OK” after including all directories. []

3c. You are now ready to build your module. Right-click on the module and click “Make module pentaho-platform-api”. You should get the following with only warnings.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.