|
|
Meister's Build Management and Apache Ant OpenMake Meister leverages the power of Ant through Build Services and methods. Developers who are accustomed to using Ant to write build.xml scripts will be able to write re-usable Ant Build scripts using the Meister Build methods. Once written, the Build Method can be used by developers across the java development enterprise creating a level of agility not normally found in ad hoc Ant scripts. The use of Ant within the Meister Build Services provides two distinct advantages: - Ant is well established as a "front-end" to Java compiles, and is well understood by Java Developers. Using Ant with Meister allows for dynamic builds using a common framework.
- The developer only has to learn one set of options for Java compiles: the Ant options. These options will be configured globally in the Build Methods, or locally in the Target Definition File.
Ant serves as an important tool for building Java components. OpenMake Meister integrates with Ant, allowing our users to define Build Methods that call Ant Tasks. Using Build Methods also allows our users to define build best practices around the usage of Ant. Below are a list of the Build Methods using Ant Tasks that are provided "out of the box". Of course, you can write your own Build Methods as you see fit. Ant Classic Java Task | Ant Copy Task | Ant Copy Task | Ant Ear Task | Ant Ear Task | Ant Jar Task | Ant Jar Task | Ant Javac Task | Ant War Task | Ant Zip Task | Ant Update Properties in Jar Task | Ant Update Deploy Task | Ant Tar Task | Ant Javadoc | Ant Javah | JUnit Test | Ant Rmic Task | |
Look for support of generating IVY dependency files in our 7.2 release. Meister understands the dependencies without needing a developer to manually create the IVY files. 7.2 will support the creation of IVY files so that they can be read by IVY.
|
|
 |
LOGIN |
 |
CONTACT US |
|
RSS |
What are Plug-ins Plug-ins are the connectors that join the tasks within the application lifecyle. Starting with Development Plug-ins, IDE project files are used as the basis for automatically generating build scripts. Development Plug-Ins standardize your builds inside or outside of the IDE creating an easy transition from a point and click build to a continuous integration build. Source Code Control and deployment plug-ins support the workflow steps that occur before and after your build. From code check-outs and executable check-ins to calling testing and deployment tools, SCM and Deployment plug-ins create the workflow that supports your continuous process automation. |
|
|