Pentaho Data Integration ( ETL ) a.k.a Kettle
- assemblies: Project distribution archive is produced under this module
- core: Core implementation
- dbdialog: Database dialog
- ui: User interface
- engine: PDI engine
- engine-ext: PDI engine extensions
- plugins: PDI core plugins
- integration: Integration tests
- Maven, version 3+
- Java JDK 1.8
- This settings.xml in your /.m2 directory
Build for nightly/release
All required profiles are activated by the presence of a property named "release".
$ mvn clean install -Drelease
This will build, unit test, and package the whole project (all of the sub-modules).
The artifact will be generated in: target
Build for CI/dev
The release builds will compile the source for production (meaning potential obfuscation and/or uglification).
To build without that happening, just eliminate the release property.
$ mvn clean install
Build a subset of modules
TODO: list profiles
Unit tests
This will run all tests in the project (and sub-modules).
$ mvn test
If you want to remote debug a single java unit test (default port is 5005):
$ cd core
$ mvn test -Dtest=<<YourTest>> -Dmaven.surefire.debug
Integration tests In addition to the unit tests, there are integration tests in the core project.
$ mvn verify -DrunITs
To run a single integration test:
$ mvn verify -DrunITs -Dit.test=<<YourIT>>
To run a single integration test in debug mode (for remote debugging in an IDE) on the default port of 5005:
$ mvn verify -DrunITs -Dit.test=<<YourIT>> -Dmaven.failsafe.debug
IntelliJ
- Don't use IntelliJ's built-in maven. Make it use the same one you use from the commandline.
- Project Preferences -> Build, Execution, Deployment -> Build Tools -> Maven ==> Maven home directory
- Submit a pull request, referencing the relevant Jira case
- Attach a Git patch file to the relevant Jira case
Use of the Pentaho checkstyle format (via mvn site and reviewing the report) and developing working
Unit Tests helps to ensure that pull requests for bugs and improvements are processed quickly.