IVYizing a Project

Owned by Former user (Deleted)
Last updated: Aug 29, 2008 by Former user (Deleted)Version comment
1 min read

Step 0
    * Run the old build - this will give you a good clue of the items
      you are trying to reproduce (and make sure it works)

Step 1
  Move the existing build files to dev_build
    * build.xml
    * build.properties

  Update the old build.xml (dev_build.xml) to use the dev_build.properties

Step 2
    * Change the eclipse bin directory to eclipse-bin

Step 2
  Copy the following files from another project (like bi-platform-api)
    * build.properties
    * build.xml
    * common_build.xml
    * ivysettings.xml
    * ivy.xml

Step 3
  Update the build.properties file
    * Update the settings as defined in the

Step 4
  Run a compile target - it should work since we aren't getting the new jars
  and the old jars should still exist in the lib directory.

What do i put in the conf attribute of my dependency in ivy.xml?

The following are the standard IVY configurations Pentaho projects should use:

  • default - alias for Compile dependencies. Your compile will break without these jars, e.g. pentaho-bi-platform-api.jar
  • test - jars that your project needs in order to compile and run your tests, excluding the dependencies in runtime
  • runtime - your app or library requires these jars/libraries in order to run, but it will compile just fine without them
  • codegen - needed for your app or library to generate/translate source code
  • debugtools - used by developers in a debug environment, not needed for compiling or running

You can follow this flowchart to help figure out what configuration your jar file belongs in:

Â