RAD Builder Plugin

This plugin allows Hudson to invoke IBM Rational Application Developer 7.0/7.5 as a build step.

New homepage
This plug-in is being maintained by its owner/maintainers from a new home. The plug-in is still compatible with Hudson, however, the entry points for documentation and issue reporting have been combined in order to provide a single point of entry.


Plugin Information

Plugin ID rad-builder
Latest Release 1.1.4
Latest Release Date Mar 04, 2011
Sources [External]
Support Eclipse Hudson Forum
Issue Tracking Eclipse Bugzilla

Labels:

plugin-builder plugin-builder Delete
tier3-compat-plugin tier3-compat-plugin Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.
  1. Apr 05, 2010

    Stephen Callaghan says:

    I'm confused how the "workspace" works here. I had thought that I was checking o...

    I'm confused how the "workspace" works here. I had thought that I was checking out the whole RAD workspace, that being the case, why does the plugin create a new workspace as a subdirectory to my hudson one or set one up elsewhere? I have build scripts that all work fine, linkage to 7.5 has been setup correctly, but I cant workout how to execute the scripts in the right project.

    Apologies as I realise this is probably something really simple! Any help much appreciated.

    1. Apr 06, 2010

      Romain Seguy says:

      There are two kinds of workspaces there: The Hudson job one and the RAD one. By ...

      There are two kinds of workspaces there: The Hudson job one and the RAD one.
      By default, the plugin will create from scratch a new RAD workspace to ensure it is clean and good for use before using it (this RAD workspace is placed within the Hudson job workspace). It is then the responsibility of the RAD build file to set up the RAD workspace as expected, generally using EPF files. It makes sense to have such a behavior to ensure developers comply with rules formalized in these EPF files (+ it saves you from uploading the big .metadata folder).
      It's anyway still possible to not use this automatically generated RAD workspace (which is, finally, just a simple folder): Just uncheck the various "Remove ..." options and make the "RAD workspace" field point to your existing RAD workspace (this path is then relative to the workspace of the Hudson job).