Plugins for Automating Software Compiles

Compile Plugins for Complex Java Builds

Dependency Management, Deployment Descriptors, Acceleration

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.

Enterprise Platform Support

Meister supports Build Automation for multiple platforms including Windows, Unix, AIX, Linux, z/Linux and z/OS, and can support a build that includes cross platforms with cross platform dependency management.

Platform Support Includes:

  • IBM WebSphere
  • Jetty, Tomcat
  • Microsoft IISMicrosoft SQL Server
  • Eclipse and .Net IDEs
  • Oracle, Sybase
  • Unix C, C++, C#, Java, COBOL, Assembler
  • Windows 2008, Windows 2012
  • Solaris, HP-UX, AIX, Linux
  • Ubantu, Redhat, SuSe, Debian
  • z/OS