Compiling Java applications using AllFusion Harvest Change Manager Option for Openmake 6.3 plugin for Eclipse/IBM Websphere Application Developer 5.x

Document ID : KB000055566
Last Modified Date : 14/02/2018
Show Technical Document Details

OPENMAKE

AllFusion Harvest Change Manager Openmake Option (AllFusion Harvest CM Openmake) is a build management tool that can be used enterprise wide to address build automation in a development environment across a variety of platforms. AllFusion Harvest CM Openmake supports a multitude of compilers thus providing a single mechanism of build management all the while centralizing Meta information in a single area. This document entails a Java build performed in Eclipse 3.0 using the AllFusion Harvest CM Openmake plugin 1.0.4 for Eclipse. Basic AllFusion Harvest CM Openmake functionality, components and introductory specifications are beyond the scope of this document.

BRIEF OVERVIEW

Java builds in AllFusion Harvest CM Openmake 6.3 are performed in conjunction with Ant 1.4.1 outside of the Eclipse tool. Ant is a make tool written in Java that makes the required processing calls for the build by using a configuration XML script, calling out a target tree where various tasks get executed. AllFusion Harvest CM Openmake constructs and provides the dynamic XML configuration script to Ant which provides the robust functionality to preprocess and run the appropriate instructions to Java. When AllFusion Harvest CM Openmake is used for Java builds within an IDE (i.e Eclipse, WSAD), no additional Ant build scripts are utilized; the full build is compiled using the existing scripts.

Please follow the Development Guide.pdf document provided with the AllFusion Harvest CM Openmake cd for more information on how to install the AllFusion Harvest CM Openmake plugin 1.0.4 with Eclipse. You will also need to have the commandline client for AllFusion Harvest CM Openmake installed on the windows box where the build will be running.

GETTING STARTED

Tyrant is a 'roguelike' adventure game written completely in Java. This application is used in order to provide an example of how a Java project can be compiled under AllFusion Harvest CM Openmake using Eclipse.

  1. Create an AllFusion Harvest CM Openmake Build Project for Tyrant.

    The build project that is associated with the Tyrant Java application needs to be created in order to allow the AllFusion Harvest CM Openmake plugin to generate the TGT files. When the AllFusion Harvest CM Openmake build project is created, the search path for the project must also be defined.

    1. Log on to the AllFusion Harvest CM Openmake web client by typing in the appropriate URL. Create a new build project.


  2. Create a new search path on the next screen. The search path may be named any arbitrary name, 'Development' will be used by default. In order for the AllFusion Harvest CM Openmake Eclipse plugin to interact with the AllFusion Harvest CM Openmake build project, the following four search path entries must be set.

    $(TARGET_DEFINITION)
    $(WORKSPACE_ROOT)
    $(WAS_PLUGINDIR)
    JAVA DIRECTORIES

$(TARGET_DEFINITION) refers to the location where the tgt's are located. The value for this variable is set dynamically by the plugin. This variable needs to be created on the build machine.

$(WORKSPACE_ROOT) refers to the location where the Eclipse workspace resides. The value for this variable is set dynamically by the plugin. This variable needs to be created on the build machine.

$(WAS_PLUGINDIR) needs to be set on the build machine to point to the appropriate WSAD libraries. This variable and its value needs to be defined on the build machine.

JAVA DIRECTORIES need to be set to point to the relative Java installation to be utilized. This may be set using $JAVA_HOME\lib and $JAVA_HOME\jre\lib or may be imported from another project if defined. This step is not necessary if the variables are defined in the environment.

Figure 1

  • Import the source code for Tyrant in Eclipse.

    1. Create a Java project in Eclipse. Name it 'Tyrant'.


  • Import the source from the file system into 'Tyrant'.

    • Highlight 'Tyrant', right-click and choose 'Import'.
    • Choose 'File system' from next dialog.
    • Browse to the source folder using 'From directory'.
    • Check the Tyrant directory on the left and click on 'Finish'.

  • If Openmake is not part of the main Eclipse menu on top then do the following.

    • Choose 'Window->Customize Perspective'. Select Openmake from the 'Shortcut categories' list.

      Figure 2


  • Select the 'Commands' tab and check 'Openmake Action Set' from the 'Available command groups'. Click on OK to exit.

  • Create an AllFusion Harvest CM Openmake Build project in the IDE.

    1. Click on 'File->New->Project'. Make sure the check box for 'Show all wizards' is selected.


  • Choose 'Openmake->Build Project' and click on next.

    • Name the Openmake project in the 'Project Name' dialog box. Name it 'Openmake_Tyrant'. Click on next.
    • Select the 'Tyrant' project as the reference in the 'Referenced projects' dialog. Click on next.
    • Choose the 'Tyrant' project defined and highlight 'Development'. Type the name of the search path in the 'Name of Build Job' box. Click on next.
    • Specify the 'Target Definition Directory'. This is named as 'tgt' by default. Choose the build directory. This is set to 'build' by default. Click on next.
      Figure 3
    • Set the bldmake commands if not set already to

      'bldmake "TYRANT" "DEVELOPMENT" -s'

      Select the om tab. Set the om commands if not set already to the following.

      'om -ov -j'

      Click on 'Finish' to exit.

  • Running the Build.

    1. Right click on 'Openmake_Tyrant' and choose 'Openmake->Generate Openmake TGT's'.


  • Right click on 'Openmake_Tyrant' and choose 'Openmake->Build with Openmake'

The build will start running in the 'Openmake Console' window. You should receive the following result as shown in the picture below.

Figure 4

For Commandline builds, the $(TARGET_DEFINITION) and the $(WORKSPACE_ROOT) variable values need to be physically defined. Once this done, the commandline build may be run using the same bldmake and om commands as above.
'bldmake "TYRANT" "DEVELOPMENT" -s'
'om -ov -j'

The result of the build should be the same as above. The class files will be packaged in the resulting Tyrant.jar in the build directory.