Non-Stop Continuous Integration Mash-up Builds

Use OpenMake Meister to mash-up your individual IDE Build with the Continuous Integration or "team" build. Meister extends the IDE's automatic code creation features out to the build scripts for non-stop CI build support. For Java developers using popular IDEs such as Eclipse and IBM-RAD, this means that executing builds outside of the IDE is 100% consistent with the builds executed inside of the IDEs. So go ahead and refactor -Meister will update the build scripts for you.

Fast Continuous Integration Builds with Build Avoidance

In the Java development environment, developers often strive to perform lean development techniques that demand the continuous integration of source code changes. In addition, lean methodologies often involves managing scheduled builds in a parallel development effort while maintaining multiple production releases simultaneously. Openmake Meister facilitates a Java build environment that supports these type of programming practices.

Meister's on demand dependency discovery allows for a true incremental build capability turning builds that run 8 hours into builds that run as short as 10 minutes, OR LESS. Get your builds running with Build Avoidance and start building continuously with accuracy.

Snychronizing Individual Builds with Team Builds

Meister directly benefits Java developers working in a team environment by synchronizing the individual developer's IDE build with the team build executed outside of the IDE in a continuous build process. Through this synchronization, Java developers are able to coordinate the introduction of changes into the build inside or outside of the IDE. Meister uses an innovative method of knowledge gathering to integrate builds and to predict build impact. Meister easily supports Lean Methodologies as well as those environments where the development to deployment lifecycle is strictly monitored and audited.

Build Best Practices

Standardize the way your Ant build scripts are designed. With Meister's Build Services, you can write a single build script that will support hundreds of Jars, Wars and Ears in exactly the same way with no redundant scripting. Support your lean methodology techniques by eliminating the confusion and redundancies often found in ad hoc scripts. Write one script to support many builds versus one script to support one build.

Multi-language Builds

As Java applications become more complex, it is not unusual for them to require calls to libraries written in standard C or C++. Meister can perform a build that will create, C, C++ or Java targets. This flexibility means that development teams no longer need to write one part of the build process in traditional Make and the Java portion in XML and ANT. Meister can handle multiple development tools in one build pass.

Customization through the SDK, Plug-ins and Build Methods

Meister provides an open SDK that allows Java developers to customize the build process to fit their unique development needs. Meister supports a wide variety of development tools and compilers without any customization requirements using Plug-in. In addition, developers can write their own reusable Build Methods to standardize their build process according to their needs and demands.

Management of Deployment Descriptors

IT professionals have learned that managing the deployment of JEE applications in large enterprise environments is a complex and expensive process. The expense comes from the technical complexity of deploying applications to multiple server environments where run-time parameters, contained within the Enterprise Application Archive (EAR) file must be uniquely configured for each server. With Meister, creating multiple deployment descriptors for a single application is substantially simplified through the use of the Deployment Descriptor Build Methods. Each Meister build can create multiple deployable EAR files, each containing the correct version of the Deployment Descriptor. For large enterprises, this ability is critical in order to avoid costly deployment mistakes or costly manual scripting to fix the problem.

 Refactoring Builds

Meister recognizes when a developer has refactored their code through the IDE.  Meister supports the refactoring process by automatically updating the build scripts to reflect the changes caused by the refactoring process.  Updates to the build scripts are done with a simple click of a button inside the development IDE through Meister plug-ins.