OpenMake Meister

Setting Default Build Project Properties

 

The default settings for Build Projects can be adjusted via Preferences.

 

 

Table PB-16 Setting Default Build Project Properties

Step

Action

1

Go to Window > Preferences

2

Select and expand Meister

3

Select Build Configuration for bldmake, om, Pre-Build, Post-Build defaults

4

Select Build Project for Build Directory Defaults

5

Select Project Nature Mappings for Nature Mapping defaults

6

Click on “Apply to Existing Projects” button to apply all defaults to all build Projects in the Eclipse Workspace

 

 

 

Table PB-17  Configuring a Build using the Plug-In

Step

Action

1

Right click the desired Project and click New – Build Project.

2

From the Project Name Screen enter a project name.  This project name does not need to match the precise name of a Project but it should have a logical name that represents the Targets you want to build inside of Eclipse.  Click Next to continue.

3

From the Project References screen, select the Eclipse projects you want associated with the build. Use the Select All button to select all projects in the workspace. Click Next to continue.

4

The Plug-in analyzes the dependency relationships between referenced projects to determine if any circular dependencies exist.

5

From the Configure Project References screen you will need to specify Build Service Mappings for each referenced Project.  Select the project reference you want to configure, and click Edit. From the Build Service Mapping" window, select a mapping from the "Configured Mappings" drop down. This field is populated by default Build Service mappings and any mappings that have been created since the plug-in was installed. If the referenced project has a Custom Build Service Mapping associated with it, it will also appear in the drop down.  If your referenced Project contains a circular dependency with another project, only Mappings that support circular dependencies will appear. If the referenced Project is not a circular dependency, only Mappings that do not support circular dependencies will appear. Please refer to the Setup and Installation section for more information on creating Custom Build Service Mappings.

 

If you want the plug-in to make a "best guess" for mappings for each Project, click the Derive Mappings button. Please note that the plug-in can only make a "best guess" for derived mappings. You should double check each project to verify that the mapping is correct.

6

From the Meister Build Settings screen you need to select the Project and Dependency Directories that are associated with the build.  It is important that the Dependency Directories are setup correctly so that the Plug-In can find the source code at build time.

7

Enter the Workflow name that you want associated with your build.  By having this association, you will later be able to execute the same Workflow from the outside of Eclipse.  Click Next to continue.

8

From the Build Directories screen, you need to specify the directories you want the Plug-In to place constructed build components.  The Target Definition Directory will store all Targets generated by the Plug-In.  These Targets need to be picked up by the Dependency Directories at build time, so the directory will have to be referenced in the Dependency Directories for the Project.

 

Click the check box for Automatically Update Target Definition Files to enable the Plug-In to update Targets on specific actions that affect them.

 

If you want to run Plug-In Builds in addition to Eclipse Builds whenever a build is executed click the check box Automatically Build With Meister.

 

Click Next to continue.

9

From the Build Configuration screen, you can enter any commands you want passed to bldmake and om at build time.  You also have the option to add any pre-Build or post-Build commands you would like executed.  To preview the list of build command calls, click on the Preview Build button.  Click Next to continue.

 

 

You can use any Build Service that is defined on the Knowledge Base server to create the results of build in the correct file name and location. In order to utilize a Build Service for an Eclipse project, you must create a "mapping" between a Build Service and an Eclipse project you want to build. This mapping enables the Build to use source created in one location based on the Eclipse project to be built and place in a different output location for the results of the Build.  The Eclipse plug-in comes loaded with three "default" Build Service mappings: Java Jar, Java War, and Java Ear. These mappings do not need to be adjusted.

 

To use a Build Service for a project simply associate a project with a Build Service mapping on the Build Service Mappings page when you set up a Build Project. The following table details how Eclipse project types correspond to Build Services:

 

Table PB-18 Default Eclipse project to Build Service Mapping

Project Type

Mapping

Java

Default Java Jar

Application Client

Default Java Jar

EJB

Default Java Jar

Web Application

Default Java War

Enterprise Application

Default Java Ear

 

You can create additional Build Service Mappings through the plug-in for Eclipse projects that do not correlate directories and dependencies to the default Build Services. 

 

 

Table PB-19 Updating Build Project Properties

Step

Action

1

Right Click on the Build Project

2

Select “Properties” from the pull down menu.

 

 

Table PB-20  Plug-In build properties

Project Settings

Settings for Meister Project and Dependency Directories that are associated with the build.  Also, Workflow names can be changed from this screen.

Build Directories

This screen shows the directories where Plug-In components are placed.  The Target Definition Directory stores all TGT’s generated by the Plug-In and the Build Directory stores built Targets.  Two check boxes “Automatically update Target Definition Files” and “Automatically Build With Meister Build” are also available from this screen.

Bldmake

Commands can be passed here to bldmake and build time.

Om

Commands can be passed here to om and build time.

Pre-Build

Pre-Build Commands can be passed here to bldmake and om.

Post-Build

Post-Build Commands can be passed here to bldmake and om.

Nature Mappings

The “Build Service Mappings” screen will display all mappings of Application Developer natures to Build Services.  These values will already be set and need not be altered. 

 

 

Table PB-21 Setting Default Build Project Properties

Step

Action

1

The default settings for Build Projects can be adjusted via Preferences:

Go to Window – Preferences

2

Select and expand Meister

 

Table PB-22 shows how the preference panels correspond to the following Build Project property panels:

 

Table PB-22 Preference Panels to Build Project Properties

Build Configuration

bldmake, om, Pre-Build, Post-Build

Build Project Directories

Build Directories

Project Nature Mappings

Nature Mappings

 

Any adjusted settings can be applied to all build Projects in the Eclipse Workspace via the “Apply to Existing Projects” button on the main Meister Preference panel.