Plugins for Automating Software Compiles

Free Java Compile Plugins

Plugins to Covers Most of Your Java Compile Needs

Plugins automate the compile logic for Java artifacts. Java developers face specific challenges when defining the compile and build process of their applications, including the management of source and library dependencies, the need for accelerating the compile and archive steps, building consistently inside and outside the IDEs, and the management of deployment descriptors.  Meister addresses these and other challenges, supporting a simplified Java development practice. Meister's benefits for the Java developer include:
  • Java Build Acceleration
  • Build best practices and standards
  • Transitive Dependency Management
  • Refactoring support in the Build
  • Management of Deployment Descriptors
  • Customizations

The following Java Plugins are included for Free:

Name

Description

Ant Java Doc 

Used to create documentation using the Ant Javadoc task.  It generates an index.hml file.  This file's timestamp is compared against Java and Classpath dependencies' timestamps in incremental builds. Because a standard file name "index.hml" is used for all JavaDoc Targets, it is recommended that each Javadoc Target be created in a separate directory, e.g. javadoc1/index.html, javadoc2/index.html, etc. 

Java Set Classpath

.classpath Builds a .classpath file. It uses the Set Classpath to resolve all classpath files. The result can then be included in a different TGT.

 Java 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 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 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 Javadoc

Used to create documentation using the javadoc program.  It generates an index.hml file.  This file's timestamp is compared against Java and Classpath dependencies' timestamps in incremental builds. Because a standard file name "index.hml" is used for all JavaDoc Targets, it is recommended that each Javadoc Target be created in a separate directory, e.g. javadoc1/index.html, javadoc2/index.html, etc.Because of the wide variation in the use of the Javadoc command, customization of the JDK Javadoc Task may be required. There will be no need to modify the Java Javadoc Build Service The Target Name should be index.html or <subdirectory>/index.html.  Typical Tasks would be 1. Set Classpath, 2. JavaDoc.

 Java Javadoc Jar

Used to create documentation using the javadoc program.  Generates an index.hml file.  This file's timestamp is compared against Java and Classpath dependencies' timestamps in incremental builds. Because a standard file name "index.hml" is used for all JavaDoc Targets, it is recommended that each Javadoc Target be created in a separate directory, e.g. javadoc1/index.html, javadoc2/index.html, etc.Because of the wide variation in the use of the Javadoc command, customization of the JDK Javadoc Task may be required. There will be no need to modify the Java Javadoc Build Service The Target Name should be index.html or <subdirectory>/index.html.  Typical Tasks would be 1. Set Classpath, 2. JavaDoc.

 Java Compile

Uses the Ant "javac" task to compile Java code files.  All dependencies added to this Build Task will be compiled using the compiler specified in the "compiler" Option parameter. 

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