Topics include Build Acceleration, CD Integration, News, and Tricks.
Meister allows you to add 4GL and Mobile compile requirements to your build automation using plugins.
Name | Description |
Lawson | Compiles Lawson objects using the Lawson compiler in headless mode. |
Adobe Flex | Compiles Adobe Flex objects. |
PeopleSoft Cobol Native Runtime | Creates MicroFocus COBOL generated native code (GNT) files from COBOL files. The target extension is '.gnt' and the source files are either .cbl or .cob. The flags chosen come from the pscbl.mak script that comes with PeopleSoft on UNIX. |
PowerGen | Creates an executable from PowerBuilder project using PowerGen. |
Actuate6 | Reports Actuate6 report compiler. Creates and .rox |
Cognos Powerhouse Compile Takes | Cognos Powerhouse files (.qzs, .qks, .qts) and passes them to their respective compilers. Then it prints both the input passed to the compilers and the output of each of the compilers to a .cognos_log file. |
Informix 4ge Executable .4ge | Creates an executable target from Informix and c code using the c4gl compiler. It is broken into two tasks; Compile and Link. The Compile Build Task converts source code to .o object files. The Link Task links .o object files and .a archive libraries to create the Final Target executable. |
Informix Archive Library | Compiles source code with the c4gl compiler and bundles the objects into an archive library using the GNU ar program. |
Informix 4ge Executable | .4ge Creates an executable target from Informix and c code using the c4gl compiler. It is broken into two tasks; Compile and Link. The Compile Build Task converts source code to .o object files. The Link Task links .o object files and .a archive libraries to create the Final Target executable. |
Informix Form Compiler .frm | Creates an Informix form target from .per files using the form4gl compiler. There is only one task which compiles .per files into .frm files. |
Informix noext Executable .noext | Creates an executable target from Informix and C code using the c4gl compiler. It is broken into two tasks; Compile and Link. The Compile Build Task converts source code to .o object files. The Link Task links .o object files and .a archive libraries to create the Final Target executable. |
Informix Object | Creates an object target from Informix or C code using the c4gl compiler. |
Informix Shared Library. .so | Creates a standard shared library using the gcc program. |
Meister enhances build automation by allowing you to incorporate database updates in your compile logic. The following Plugins can be purchased to extend your library of reusable Build Tasks.
Name | Description |
Oracle Cobol Exe | Creates a standard executable linked statically and dynamically with Oracle libraries. For pre-compiling, it calls the Oracle proc program. For C and C++, it executes the xlc compiler. For COBOL programs, it uses the Microfocus COBOL compiler, cob. For creating the executable, it uses the Microfocus COBOL compiler, cob, to link. |
Oracle Exe | Creates a standard executable. For pre-compiling, it calls the Oracle Pre-Compiler. For C and C++, it executes the cc compiler. For creating the executable, it uses oraxlc to compile and link. |
Oracle Forms | The Oracle forms compiler, ifcmp60 on Windows and f60gen for other OS's, is used to create form objects from .fmb files. |
Oracle Form Library | The Oracle forms compiler, ifcmp60 on Windows and f60gen for other OS's, is used to create form libraries (.plx) from .pll files. |
Oracle PSQL | Compiles PL/SQL into an Oracle database. A file with .sqo extension is created to represent a successfully compiled object on the file system. The timestamp of the dependency .sql files will be checked against the .sqo file for incremental builds. If the .sql file is later than the .sqo, then it will be recompiled and a new.sqo file created. sqlplus is used to compile the code. |
Oracle Report | Uses the Oracle Reports compiler, rwcon60, to create .rep reports. .rdf files may also be created. |
Oracle TDF | Uses the Oracle Reports compiler, rwcon60, to create TDF reports. .rdf and .rex files may also be created. |
Oracle Request Router | An example of a customized Oracle C and C++ executable. It uses xlc/xlC to compile source code and ld to link the objects into an executable. |
Sybase ASE 12.5 and Greater | Used to create Sybase Adaptive Server database objects. It uses files to represent compiled objects and uses the isql program for compiling DDL, SQL and T/SQL. It uses the bcp command to import and export data. Designed for use with ASE 12.5 and greater. Beginning in ASE 12.5, ALTER statements can be bundled in a single transaction. You must have the "use ddl in tran" option set to true. To set this, issue the following commands at the Sybase command line: use db_name go sp_dboption db, "use ddl in tran", true go Start by create a final target file name with '.complete' extension. The name can be anything and can be related to a change request, e.g. SCR0345.complete This file will be created only after all the operations have completed successfully. Then add individual file dependencies broken down into single files as dependencies in the different option groups. Note that different types of DDL statements must have different file extensions according to the rules. |
Sybase ASE pre-12.5 | Used to create Sybase Adaptive Server database objects. It uses files to represent compiled objects and uses the isql program for compiling DDL, SQL and T/SQL. It uses the bcp command to import and export data. Designed for use with ASE prior to release 12.5 because of the inability to bundle multiple ALTER statements into a single transaction. You must have the "use ddl in tran" option set to true. To set this, issue the following commands at the Sybase command line: use db_name go sp_dboption db, "use ddl in tran", true go Start by create a final target file name with '.complete' extension. The name can be anything and can be related to a change request, e.g. SCR0345.complete This file will be created only after all the operations have completed successfully. Then add individual file dependencies broken down into single files as dependencies in the different option groups. Note that different types of DDL statements must have different file extensions according to the rules. |
DB2 Exe | Creates a standard executable by using DB2 Prep to pre-compile the .SQC file. Uses cc to compile the C programs. Uses xlc for linking. |
DB2 shared library | Creates a standard shared library by using DB2 Prep to pre-compile the .SQC file. Uses cc to compile the C programs. Uses xlc for linking. |
Meister’s Extended Plugins for Linux and UNIX compile needs support complex compilation tasks and includes your dependency management and acceleration. The following Plugins can be purchased to extend your library of reusable Linux and Unix Compile Plugins.
Name | Description |
AcuCobol 32 Executable | Creates a standard executable using the AcuCOBOL CCBL or CCBL32 compiler. |
Archive Library | An archive library is created by compiling source code into object files and the bundling the object files with the ar program. |
Microfocus Cobol Executable | Creates a standard executable. For C and C++, it executes the xlc compiler. For COBOL programs, it uses the Microfocus COBOL compiler, cob. For creating the executable, is uses the Microfocus COBOL compiler, cob, for linking. |
COBOL Native Runtime | This creates MicroFocus COBOL generated native code (GNT) files from COBOL files. The target extension is '.gnt' and the source files are either .cbl or .cob. The key flag is the '-u' flag which tells the compiler to create a GNT file instead of a native operating system object file. |
GNU Archive Library | Compiles source code with the gcc compiler and bundles the objects into an archive library using the GNU ar program. |
GNU CPP Executable | Creates an executable target from .c code using the gcc compiler. It is broken into two tasks; Compile and Link. The Compile Build Task converts source code to .o object files. The Link Task links .o object files and libraries to create the Final Target executable. |
GNU Executable | Creates an executable target from .c code using the gcc compiler. It is broken into two tasks; Compile and Link. The Compile Build Task converts source code to .o object files. The Link Task links .o object files and libraries to create the Final Target executable. |
GNU LD Shared Library | Creates a standard shared library using the gcc or g++ programs to compile C and C++ code and then using the AIX ld program to link the objects into a dynamic library. |
GNU Oracle ProC Executable | This creates an executable from source code by compiling the C code and linking to Oracle libraries. |
GNU PIC Archive Library | This creates a GNU archive library from source code by compiling the C/C++ code with the Position Independent Code option of the gcc compiler. |
GNU PIC Executable | This creates an executable from source code by compiling the C code with the Position Independent Code option of the gcc program. |
GNU PIC Oracle Executable | This creates an executable from source code by compiling the C code with the Position Independent Code option for gcc and linking to Oracle libraries using gcc. |
GNU Shared Library | Creates a standard shared library using the gcc program. |
ITHISAM | Creates C header files from .DDL using the ITHISAM compiler. |
LD Shared Library | This shared library explicitly uses ld in the Link Build Task. The shared library is created by using the ar command to format the final object. cc is used to compile the source code. |
LD Shared Object | This shared library explicitly uses ld in the Link Build Task. The shared library is created WITHOUT using the ar command to format the final object. cc is used to compile the source code. |
Lex and Flex C File | Used to generate a C source file from a lex source file when the C file needs to have a different name from the Lex file. There is also a Build Task under Available Tasks with the same rule that can be imported into any build service that compiles C code. |
Lex C Header File | Used to generate a C source header file from a lex source file when the C file needs to have a different name from the Lex file. There is also a Build Task under available tasks with the same rule that can be imported into any build service that compiles C code. |
Visual Age C Project Archive Library | Creates an archive library from the .icc project file. The .icc files is scanned to see if any source code has changed compared to the executable being created. |
Visual Age C Project Executable | Creates an executable target from the .icc project file. The .icc files is scanned to see if any source code has changed compared to the executable being created. |
PIC Archive Library | This creates a GNU archive library from source code by compiling the C/C++ code with the Position Independent Code option of the gcc compiler. |
PIC Executable | This creates an executable from source code by compiling the C code with the Position Independent Code option of the gcc program. |
PIC Oracle Executable | This creates an executable from source code by compiling the C code with the Position Independent Code option for gcc and linking to Oracle libraries using gcc. |
Meister supports complex .Net and Windows compiles with extended Microsoft compile plugins. The following Plugins can be purchased to extend your library of reusable Windows Build Tasks.
Name | Description |
.NET 2005 Dynamic Link Library | Serialization Creates a Serialize .NET DLL using sgen utility |
.NET 2005 Solution Dynamic Link Library | Creates a .NET DLL using a .NET Solution file as a dependency. The DLL can be VB, C#, or C++. Built against the .NET 2.0 Framework |
.NET 2005 Solution Executable | Creates a .NET EXE using a .NET Solution file as a dependency. The EXE can be VB, C#, or C++. Built against the .NET 2.0 Framework |
.NET C-Sharp Dynamic Link Library | Creates a DLL using the Microsoft .NET C# compiler. The dependency should be the .NET Project file (.csproj). Must run bldmake with -s to preserve case sensitivity |
.NET C-Sharp Executable | Creates a command line executable using the Microsoft .NET C# compiler. The dependency should be the .NET Project file (.csproj). Must run bldmake with -s to preserve case sensitivity. |
.NET C-Sharp Module | Creates a C# Module using the Microsoft .NET C# compiler. The dependency should be the .NET Project file (.csproj). |
.NET ISAPI Extended Dll Shared | Creates a Microsoft .NET Internet Server Extension (ISAPI) or Filter DLL by using the Microsoft .NET C/C++ Compiler. Does not link the Microsoft .NET runtime libraries into the executables. The runtime libraries must be distributed and loaded dynamically. The dependency should be the .NET Project file (.vcproj .vcxproj). Must run bldmake with -s to preserve case sensitivity. |
.NET ISAPI Extended Dll Static | Creates a Microsoft .NET Internet Server Extension (ISAPI) or Filter DLL by using the Microsoft .NET C/C++ Compiler. Links the Microsoft .NET runtime libraries into the executable. Does not require that the runtime libraries be distributed. The dependency should be the .NET Project file (.vcproj .vcxproj). Must run bldmake with -s to preserve case sensitivity. |
.NET Managed CPP Class Library | Creates a Microsoft .NET DLL using Microsoft .NET C/C++ compiler. The C/C++ code is .NET managed code. The dependency should be the .NET Project file (.vcproj .vcxproj). Must run bldmake with -s to preserve case sensitivity. |
.NET MFC ActiveX Control Shared Creates | ActiveX control by using the Microsoft .NET C/C++ Compiler. Does not link the Microsoft .NET runtime libraries into the executables. The runtime libraries must be distributed and loaded dynamically. The dependency should be the .NET Project file (.vcproj .vcxproj). Must run bldmake with -s to preserve case sensitivity. |
.NET MFC ActiveX Control Static | Creates a ActiveX control by using the Microsoft .NET C/C++ Compiler. Links the Microsoft .NET runtime libraries into the executables. Does not require that the Microsoft .NET runtime libraries be distributed. The dependency should be the .NET Project file (.vcproj .vcxproj). Must run bldmake with -s to preserve case sensitivity. |
.NET MFC Dll Shared | Creates a Microsoft .NET DLL with extended features by using the Microsoft .NET C/C++ compiler. An extension DLL allows you to derive custom classes from MFC and lend this "extended" version of MFC to applications that call your DLL. Extension DLLs can be used for passing MFC-derived objects between the application and the DLL. Does not link the Microsoft .NET runtime libraries into the DLL. The runtime libraries must be distributed and loaded dynamically. The dependency should be the .NET Project file (.vcproj .vcxproj). Must run bldmake with -s to preserve case sensitivity. |
.NET MFC Dll Static | Creates a standard Microsoft .NET executable by using the Microsoft .NET C/C++ Compiler and the Microsoft Foundation Class Libraries. Links the Microsoft .NET runtime libraries into the DLL. Does not require that the Microsoft runtime libraries be distributed. The dependency should be the .NET Project file (.vcproj .vcxproj). Must run bldmake with -s to preserve case sensitivity. |
.NET MFC Exe Shared | Creates a standard Microsoft .NET executable by using the Microsoft .NET C/C++ Compiler and the Microsoft Foundation Class Libraries. Does not link the Microsoft .NET runtime libraries into the executables. The runtime libraries must be loaded dynamically. The dependency should be the .NET Project file (.vcproj .vcxproj). Must run bldmake with -s to preserve case sensitivity. |
.NET MFC Exe Static | Creates a standard Microsoft .NET executable by using the Microsoft .NET C/C++ Compiler and the Microsoft Foundation Class Libraries. Links the Microsoft .NET runtime libraries into the EXE. Does not require that the Microsoft runtime libraries be distributed. The dependency should be the .NET Project file (.vcproj .vcxproj). Must run bldmake with -s to preserve case sensitivity. |
.NET Solution Installer | Creates a MSI file using a .NET Solution file as a dependency. |
.NET Visual Basic Dll | Creates a standard Visual Basic .NET dynamic link library. The dependency should be the .NET Project file (.vbproj). Must run bldmake with -s to preserve case sensitivity. |
.NET Visual Basic Exe | Creates a standard Visual Basic executable. The dependency should be the .NET Project file (.vbproj). Must run bldmake with -s to preserve case sensitivity. |
.NET Win32 Console Shared | Creates a command line program using the Microsoft .NET C/C++ compiler. Does not link the Microsoft .NET runtime libraries into the executables. The runtime libraries must be distributed and loaded dynamically. The dependency should be the .NET Project file (.vcproj .vcxproj). Must run bldmake with -s to preserve case sensitivity. |
.NET Win32 Console Static | Creates a command line program using the Microsoft .NET C/C++ comiler. Links the Microsoft .NET runtime libraries into the executable. Does not require that the runtime libraries be distributed. The dependency should be the .NET Project file (.vcproj .vcxproj). Must run bldmake with -s to preserve case sensitivity. |
MFC AppWizard Dll Shared | Creates a standard Microsoft DL by using the Microsoft Foundation Class Libraries.Does not link the Microsoft runtime libraries into the executables. The runtime libraries must be distributed and loaded dynamically. |
MFC AppWizard Dll Static | Creates a standard Microsoft DLL by using the Microsoft Foundation Class Libraries. Links the Microsoft runtime libraries into the DLL. Does not require the Microsoft runtime libraries be distributed |
MFC AppWizard Exe Shared | Creates a standard Microsoft executable by using the Microsoft Foundation Class Libraries. Does not link the Microsoft runtime libraries into the executables. The runtime libraries must be loaded dynamically. |
MFC AppWizard Exe Static | Creates a standard Microsoft executable by using the Microsoft Foundation Class Libraries. Links the Microsoft runtime libraries into the EXE. Does not require that the Microsoft runtime libraries be distributed. |
MFC AppWizard Extended Dll Shared | Creates a Microsoft DLL with extended features. An extension DLL allows you to derive custom classes from MFC and lend this "extended" version of MFC to applications that call your DLL. Extension DLLs can be used for passing MFC-derived objects between the application and the DLL. Does not link the Microsoft runtime libraries into the executables. The runtime libraries must be distributed and loaded dynamically |
MFC AppWizard Ocx Shared | Creates a Microsoft ActiveX module. Does not link the Microsoft runtime libraries into the executables. The runtime libraries must be distributed and loaded dynamically. |
MFC AppWizard Ocx Static | Create a Microsoft ActiveX module. Links the Microsoft runtime libraries into the executable. Does not require that the runtime libraries be distributed. |
MSVC Application Shared | Creates a standard Microsoft Executable. Does not link the Microsoft runtime libraries into the executables. The runtime libraries must be distributed and loaded dynamically. |
MSVC Application Shared NoPCH | Creates a standard Microsoft Executable. Does not use precompiled header files. Does not link the Microsoft runtime libraries into the executables. The runtime libraries must be distributed and loaded dynamically. |
MSVC Application Static | Creates a standard Microsoft Executable. Links the Microsoft runtime libraries into the executable. Does not require that the runtime libraries be distributed. |
MSVC ATL COM AppWizard Dll | Creates a Microsoft ATL COM interface DLL. Does not link the Microsoft runtime libraries into the executables. The runtime libraries must be distributed and loaded dynamically. |
MSVC COM Dll Shared | Creates a Microsoft COM interface DLL. Does not link the Microsoft runtime libraries into the executables. The runtime libraries must be distributed and loaded dynamically. |
MSVC COM Dll Static | Creates a Microsoft COM Interface DLL. Does not require that the runtime libraries be distributed. |
MSVC Console Static | MSVC Console Static Creates a command line executable. Links the Microsoft runtime libraries into the executable. Does not require that the runtime libraries be distributed. |
MSVC Dynamic Link Lib Shared | Creates a standard Microsoft DLL. Does not link the Microsoft runtime libraries into the executables. The runtime libraries must be distributed and loaded dynamically. |
MSVC Dynamic Link Lib Shared NoPCH | Creates a standard Microsoft DLL. Does not use precompiled header files. Does not link the Microsoft runtime libraries into the executables. The runtime libraries must be distributed and loaded dynamically. |
MSVC Dynamic Link Lib Static | Creates a standard Microsoft DLL. Links the Microsoft runtime libraries into the executable. Does not require that the runtime libraries be distributed. |
MSVC Static Library | Creates a Library that contains object files. |
MSVC Threaded Console Shared | Creates a command line program that uses threads. Does not link the Microsoft runtime libraries into the executables. The runtime libraries must be distributed and loaded dynamically |
TypeLib | Creates a type library that is used to update the Windows Registry. |
VisualBasic | Creates a standard Visual Basic executable. Note: When using the OM -a flag, which forces the rebuild of a VisualBasic executable, the VisualBasic project must allow Binary Compatible compiles. Otherwise a Binary Compatible error will occur. |
Visual Basic 7 Dll | Creates a standard Visual Basic 7 dynamic link library. Note: When using the OM -a flag, which forces the rebuild of a VisualBasic executable, the VisualBasic project must allow Binary Compatible compiles. Otherwise a Binary Compatible error will occur. |
Visual Basic 7 Exe | Creates a standard Visual Basic 7 executable. Note: When using the OM -a flag, which forces the rebuild of a VisualBasic executable, the VisualBasic project must allow Binary Compatible compiles. Otherwise a Binary Compatible error will occur. |
VisualBasic DLL | Creates a standard Visual Basic dynamic link library. Note: When using the OM -a flag, which forces the rebuild of a VisualBasic executable, the VisualBasic project must allow Binary Compatible compiles. Otherwise a Binary Compatible error will occur. |
VisualBasic OCX | Creates a Visual Basic OCX control. Note: When using the OM -a flag, which forces the rebuild of a VisualBasic executable, the VisualBasic project must allow Binary Compatible compiles. Otherwise a Binary Compatible error will occur. |
Visual Basic VBC Console Exe | Compiles Visual Basic with the .NET Framework SDK compiler vbc.exe. It is used for target type 'exe'. It requires that files be listed as dependencies in the target definition file. To compile Visual Basic using a .vbp, .vbproj or a .sln file as a dependency, use the other Visual Basic Plugins. |
Visual Basic VBC Library | Compiles Visual Basic with the .NET Framework SDK compiler vbc.exe. It is used for target type 'winexe'. It requires that files be listed as dependencies in the target definition file. To compile Visual Basic using a .vbp, .vbproj or a .sln file as a dependency, use the other Visual Basic Plugins. |
Visual Basic VBC Module | Compiles Visual Basic with the .NET Framework SDK compiler vbc.exe. It is used for target type 'winexe'. It requires that files be listed as dependencies in the target definition file. To compile Visual Basic using a .vbp, .vbproj or a .sln file as a dependency, use the other Visual Basic Plugins. |
Visual Basic VBC Windows Exe | Compiles Visual Basic with the .NET Framework SDK compiler vbc.exe. It is used for target type 'winexe'. It requires that files be listed as dependencies in the target definition file. To compile Visual Basic using a .vbp, .vbproj or a .sln file as a dependency, use the other Visual Basic Plugins. |
VisualBasic VBG | Creates a standard Visual Basic executable. Note: When using the OM -a flag, which forces the rebuild of a VisualBasic executable, the VisualBasic project must allow Binary Compatible compiles. Otherwise a Binary Compatible error will occur. |
VS Devenv 2005 Solution Dynamic Link Library | Creates a .NET DLL using a .NET Solution file as a dependency. The DLL can be VB, C#, or C++. Built against the .NET 2.0 Framework |
VS Devenv 2005 Solution Executable | Creates a .NET EXE using a .NET Solution file as a dependency. The EXE can be VB, C#, or C++. Built against the .NET 2.0 Framework |
VS Devenv 2005 Solution Installer | Creates a MSI file using a .NET Solution file as a dependency. |
Borland BCC32 Dynamic Link Library | Uses ilink32 linker to combine object modules (.OBJ files), library modules (.LIB files), and resources to produce executables (.EXE, .DLL, and .BPL files). |
Borland BCC32 Executable | Creates a standard executable by using bcc32 to compile and link C and C++ programs. bcc32 defaults to calling ilink32 and processing the link automatically. |
Borland Delphi Console Executable | Creates a command line executable using the Borland Delphi Compiler. Only the Delphi Project File (.dpr) needs to be listed as a dependency. |
Borland Delphi Console Executable | Creates a command line executable using the Borland Delphi Compiler. Only the Delphi Project File (.dpr) needs to be listed as a dependency. |
Borland Delphi DLL | Creates a Dynamic Link Library (DLL) using the Borland Delphi Compiler. Only the Delphi Project File (.dpr) needs to be listed as a dependency. |
Borland Delphi GUI Executable | Creates a Windows GUI executable using the Borland Delphi Compiler. Only the Delphi Project File (.dpr) needs to be listed as a dependency. |
Borland Delphi Package | Creates a Borland .bpk. |
Microfocus Cobol Executable | Creates a standard executable using the Microfocus COBOL compiler. |
Microfocus NetExpress Cbllink | Invokes the cbllink Compiler that compiles and links source .cbl cobol files. |
Microfocus NetExpress Cbllink | Invokes the cbllink Compiler that compiles and links source .cbl cobol files. |
Microfocus NetExpress Compile | Calls the cobol, cblnames and link executables to generate final target dll's and exe's. All dependencies are chained together so that the ouput of one step will automatically be included in the next, with the exception of the cblnames ouput file "cblds.obj." As a result, "cblds.obj" needs to be added as an explicit dependency to the Link task. |
Microfocus NetExpress | Creates a Graphical Executable |
Microfocus NetExpress | Creates a Graphical SQL Executable |
AcuCobol 32 Executable | Creates a standard executable using the AcuCOBOL CCBL or CCBL32 compiler. |
The following Plugins can be purchased to extend your library of reusable Java Build Tasks. These Plugins are used to compile more complex Java artifacts and gives you the added benefit of dependency management and acceleration of the build.
Name | Description |
Java Combine ClassPath | Builds a .classpath file. It uses the Set Classpath to resolve all classpath files. The result can then be included in a different build targets. |
Java Copy | Copies dependencies to location(s) defined using the "todir=" parameter available in the pre-defined options. Multiple Option Groups may also be defined for groups of dependencies that need to copy to other "todir=" locations. The Target created in the build directory is a .copy text file containing log information. |
Java Ear as Jar | The Java Ear as Jar builds a .jar file using the .ear format. It uses the Set Classpath, Ant Javac and Ant Ear Build Tasks to compile and package up all of the dependencies that need to be included in the final target .ear file. Note that there may be no dependencies in the "Set Classpath" and "Ant Javac" Build Tasks if there is no .java source to compile for the .ear-like .jar file. All of the directory structure requirements of a .jar file are built into the Build Service. |
Java Ear no Compilation | Builds an .ear file. It uses the Set Classpath, Ant Javac and Ant Ear Build Tasks to compile and package up all of the dependencies that need to be included in the final target .ear file. Note that there may be no dependencies in the "Set Classpath" and "Ant Javac" Build Tasks if there is no .java source to compile for the .ear file. All of the directory structure requirements of a .ear file are built into the Build Service. |
Java Jar no Compilation | Builds a .jar file. It uses the Ant Jar Build Tasks to package up all of the dependencies that need to be included in the final target .jar file. |
Java Jar Update | Unjars jar dependencies and adds exploded files to target jar file. |
Java JNI | Converts a class file into a header file (.h) for the Java to Native interface. The dependency is the .class file. |
Java JUnit Test | Used to run JUnit tests. It runs JUnit tests specified in .java files in the Ant JUnit Test task against the classes and jars specified in the Set Classpath task. Each .java test file will create a corresponding output logfile using the formatter specified by the "type=" option. The JUnit Test task also creates as its target a .test logfile containing the output from Ant. By default the JUnit task runs with the options printsummary="withOutAndErr" and formatter type="xml". |
Java RMIC Jar | Incorporates a 4-step process to create a .jar file. The "Set Classpath" and "Ant Javac" Build Tasks define the classpath and compile javac files to class files as in other Plugins. The "Ant RMIC" Build Task takes as source the compiled classes from "Ant Javac" and generates other class files. The "Ant RMIC Jar" Build Task jars classes from both the "Ant Javac" and "Ant RMIC" Build Tasks. |
Java Signed Jar | Builds a .jar file. It uses the Set Classpath, Ant Javac and Ant Jar Build Tasks to compile and package up all of the dependencies that need to be included in the final target .jar file. |
Java Tar | Builds a .tar file. It uses the Ant Tar Build Task to package up all of the dependencies that need to be included in the final target .tar file |
Java War as Jar | Builds a .jar file in the format of a .war file. It uses the Set Classpath, Ant Javac and Ant War Build Tasks to compile and package up all of the dependencies that need to be included in the final target .jar file. All of the directory structure requirements of a .war file are built into the Build Service final .jar file. |
Java War no Compilation | Builds a .war file. It uses the Set Classpath, Ant Javac and Ant War Build Tasks to compile and package up all of the dependencies that need to be included in the final target .war file. All of the directory structure requirements of a .war file are built into the Build Service. |
Java WBIMB BAR File | Java Weblogic Ant wlappc Compile Prepares the compile by setting the Classpath. The Classpath should include the library containing the APPC compiler, most likely weblogic.jar. Uses Ant APPC Compile Task to compile APPC dependencies with the weblogic.appc compiler. |
Java Weblogic APPC Compile | Prepares the compile by setting the Classpath. The Classpath should include the library containing the APPC compiler, most likely weblogic.jar. Uses Ant APPC Compile Task to compile APPC dependencies with the weblogic.appc compiler. |
Java Weblogic Clientgen Jar | Uses the Weblogic clientgen task to create a client JAR file that contains a thin Java client used to invoke a Web Service. Takes an EAR file that contains the implementation of a WebLogic Web Service as a depencency.Java Weblogic EJB Compile Prepares the compile by setting the Classpath. The Classpath should include the library containing the EJB compiler, most likely weblogic.jar. Uses Ant EJB Compile Task to compile EJB dependencies with the weblogic.ejbc compiler. |
Java Weblogic EJB Compile and Jar | Builds a .jar file. It uses the Set Classpath, Ant Javac and Ant Jar Build Tasks to compile and package up all of the dependencies that need to be included in the final target .jar file.Java Weblogic JSPC Compile Prepares the compile by setting the Classpath. The Classpath should include the library containing the JSP compiler, most likely weblogic.jar. Uses Ant JSP Compile Task to pre-compile JSP dependencies with the weblogic.jspc compiler. |
Java Weblogic Servicegen Ear | Servicegen performs all Weblogic steps needed to assemble a Web Service. These steps include: - Creating the Web Service deployment descriptor (web-services.xml). - Introspecting EJBs and Java classes and generating any needed non-built-in data type supporting components. - Generating the client JAR file. - Packaging all the pieces into a deployable EAR file. |
Java Weblogic War | Builds a .war file. It uses the Set Classpath, Ant Javac and Ant War Build Tasks to compile and package up all of the dependencies that need to be included in the final target .war file. All of the directory structure requirements of a .war file are built into the Build Service. |
Java Weblogic WLI Ear no Compile | Builds an .ear file. It uses the Set Classpath, Ant Javac and Ant Ear Build Tasks to compile and package up all of the dependencies that need to be included in the final target .ear file. Note that there may be no dependencies in the "Set Classpath" and "Ant Javac" Build Tasks if there is no .java source to compile for the .ear file. All of the directory structure requirements of a .ear file are built into the Build Service. |
Java Weblogic WLI Jar | .jar Final Results Extension: .jar Builds a .jar file. It uses the Set Classpath, Ant Javac and Ant Jar Build Tasks to compile and package up all of the dependencies that need to be included in the final target .jar file. |
Java Weblogic WLI War | Builds a .war file. It uses the Set Classpath, Precompile (xmlbean and apt tasks), Ant Javac and Ant War Build Tasks to compile and package up all of the dependencies that need to be included in the final target .war file. All of the directory structure requirements of a .war file are built into the Build Service. |
Java Weblogic XMLBeans Jar | .jar Final Results Extension: .jar Builds a .jar file. It uses the Set Classpath, Ant Javac and Ant Jar Build Tasks to compile and package up all of the dependencies that need to be included in the final target .jar file. |
Java WebSphere 5.1 EJBDeploy EAR | Use this build service when developing with IBM WebSphere Studio Application Developer 5.1 to generate deployment code and classes for an EAR. The dependency is the EAR built by the Openmake Eclipse Plugin-generated target files and the output file is the deployable EAR. The WAS_HOME environment variable MUST be set, e.g. WAS_HOME=C:\Progra~1\IBM\WSADv5.1 To build a deployable EAR for the MiniBank example, use the following values in the target definition: Final Target Name: MiniBankEAR.ear Final Target Output Path: deploy Dependency: MiniBankEAR.ear |
Java WebSphere 5.1 WSEJBDeploy | Use this build type when developing with IBM Websphere Application Developer 5.1 to generate deployment code and classes.The dependency is the JAR built by the Openmake Eclipse Plugin-generated target files and the output file is the deployable JAR. The WAS_HOME environment variable MUST be set, e.g. WAS_HOME=C:\bin\WebSphere\AppServer |
Java WebSphere 6.0 EJBDeploy EAR | Use this build service when developing with IBM Rational Application Developer 6.0 for WebSphere Software to generate deployment code and classes for an EAR. The dependency is the EAR built by the Openmake Eclipse Plugin-generated target files and the output file is the deployable EAR. The WAS_HOME environment variable MUST be set, e.g. WAS_HOME=C:\bin\WebSphere\AppServer To build a deployable EAR for the AutoWorld example, use the following values in the target definition: Final Target Name: autoworld.ear Final Target Output Path: deploy Dependency: AutoWorld20ExampleEAR.ear |
Java Websphere Application Client Jar | Builds an .jar file. It uses the Set Classpath, Ant Javac and Ant Ear Build Tasks to compile and package up all of the dependencies that need to be included in the final target .jar file. |
Java Websphere Ear | Builds an .ear file. It uses the Set Classpath, Ant Javac and Ant Ear Build Tasks to compile and package up all of the dependencies that need to be included in the final target .ear file. Note that there may be no dependencies in the "Set Classpath" and "Ant Javac" Build Tasks if there is no .java source to compile for the .ear file. All of the directory structure requirements of a .ear file are built into the Build Service. |
Java WebSphere EJBDeploy Complete | Builds a .jar file. It uses the Set Classpath, Ant Javac and Ant Jar Build Tasks to compile and package up all of the dependencies that need to be included in the final target .jar file. |
Java WPS Service Deploy | Builds a .ear file. It uses the Ant Zip Build Tasks to package up all of the dependencies that need to be included in the final target .ear file and use servicedeploy to create the .ear. |
Java Zip | Builds a .zip file. It uses the Ant Zip Build Tasks to package up all of the dependencies that need to be included in the final target .zip file. |
Manage Ear Deployment Descriptors | Insert and replace XML tags and values in deployment descriptors of an archive. It unjars the files to be updated from the archive, next it will insert and replace the XML tags and values and finally create a new jar with the updated files to the Target name. |
Manage War Deployment Descriptors | Insert and replace XML tags and values in deployment descriptors of an archive. It unjars the files to be updated from the archive, next it will insert and replace the XML tags and values and finally create a new jar with the updated files to the Target name. |
MD5 Checksum | Creates a Target file with a .md5 extension that contains the MD5 checksum information of the dependent file. The checksum value is also outputted to the build log. This value is useful in determining if a Target built as expected. |
Update Deployment Descriptors | Insert and replace XML tags and values in deployment descriptors of an archive. It unjars the files to be updated from the archive, next it will insert and replace the XML tags and values and finally updated the original jar with the updated files. |