I hope this Ant WAR task example is helpful. If your Build File was generated using the default settings supplied in Run Under. In the Export Ant Scripts pane, select the projects to generate Ant scripts for and decide whether to create a workspace metadata file. Note: this simple ant instruction will work fine if there is only one target in the Build File. Generating Ant Build Scripts To Export Ant Build Scripts and (Optionally) a Workspace Metadata File Select File > Export> Click Next. This will open cmd in the directory of the Build File.
When working just on my JSP files, I always find it much faster to just copy my JSP files to the webapps folder, as compared to building the entire project, so that's where this task comes from. Highlight the full file-path by clicking in the top panel. you'll see that I also created a task just to deploy my JSP files. In the meantime, here is a sample Ant build.xml file that demonstrates the use of the Ant WAR task, and can be used to create a war file. I'm not going to provide any explanation of any of this right now, but if I have time in the future I'll come back here and add a few comments about how this build script works. What is muCommander.exe muCommander.exe is known as Java(TM) Platform SE 6 U37, it also has the following name Java(TM) Platform SE 7 U40 or Java(TM) Platform SE 8 and it is developed by Sun Microsystems, Inc., it is also developed by Oracle Corporation.We have seen about 3 different instances of muCommander.exe in different location. You'll probably have to know a little bit about Java, Ant, and build files for this sample build.xml file to be any use to you, but if you're looking for a sample Ant build script that can be used to create a war file, or one that simple uses a war task, this example might work for you.