![]() |
OpenMake Meister |
Table PB-6 defines the steps for defining a Java War Target.
Table PB-6 Defining a War Target
Step |
Action |
1 |
Go to the Target Explorer tab found under the OM Meister Perspective. |
2 |
Right Click in the left pane of the Target Explorer and Select New – Target to launch the Target Wizard. |
3 |
Select the Java Operating System and the Java War Build Service. Select Next. |
4 |
Enter the Name of your Target. It is recommended to use a name that refers to the Final Target being built, for example foo.war. Keeping the names of the Final Target and Target Definition file similar makes it easy to determine to which Final Target the Target Definition File belongs. Select Finish. |
5 |
You will now be brought to the Target Overview Screen. Enter the Project which the Target is to be associated. |
6 |
Select the Detail tab at the bottom of your screen to enter your Target's file dependencies. |
7 |
Select the Add Deps Button and enter the file name associated to each step required to build your Target. Enter the Jar Files needed by the classpath to the Set Classpath Java Task. |
8 |
Enter your Java packages needed for the compile to the Ant Javac Java Task. |
3 |
Enter your runtime Jar files to the Web-Inf Lib Option Group folder. |
4 |
Enter your HTML files that are needed to the Ant War Java Task. |
5 |
The Results from Ant Javac are added to the Ant War Java Task’s Web-Inf Classes Option Group folder. |
The resulting War file contains the HTML files from the root of the War. The class files are in WEB-INF/classes. The runtime Jar files are in WEB-INF/lib.
When adding the Java package dependencies to the Target Editor, wild cards can be used to simplify the dependency definitions. See the section Wildcards and Dependencies for details on how you can use wildcards in Java Targets.