OpenMake Meister

Java Targets

Using the Java Build Services provides build best practices needed to standardize how your Java objects are created.  When defining your unique Targets for a Java build, you will be provided with a "blueprint" structure, based on the Java Build Service selected.  You can then enter your unique Target information needed to build the Target.

A Target based on a Java Build Service uses Java Build Tasks to generate the Ant build.xml.  Java Build Tasks map one-to-one with Ant tasks.  For example, the Java Build Task called Ant Javac maps to the Ant task called Javac.  Another example is the Java Build Task called Ant War which maps to the Ant task called war. 

Within a Java Build Task an Option Group may be defined.  The Option Group enables different groups of Ant attributes to be used within the same Java Build Task. Using Option Groups provides “folders” for sets of dependencies that need to use the same Ant attributes.  When a Target is defined, the dependencies that need to use the same Ant attributes are placed into these Option Group folders.  Each dependency placed into the Option Group “folder” in the Target will use the Ant attributes defined to that Option Group.

For  example, the Meta-Inf Option Group has the Ant attribute prefix set to META-INF.  And the Web-Inf Lib Option Group has the Ant attribute prefix set to WEB-INF/lib.

As with all Targets, Java Targets are dependent upon certain files.  All files (such as an index.html) and all packages (such as com\report\*.java) that need to be compiled must be defined as dependencies assigned to the appropriate Java Task.