A target takes the form: … A target must have a name and may have several additional attributes that determine when and if the target actually gets executed. The target should contain zero or more tasks. A task is an atomic unit of work in the Ant world. Each task is bound to a Java class file that Ant executes, passing to it any arguments or subelements defined with that task. The Ant tool is extensible and allows you to create your own tasks. For this book and the Storefront example, the built-in tasks included with the Ant distribution are all you will need. If, however, you needed to create a new task, you could do so by defining the task in the build.xml file, using the taskdef task to bind the task name to a Java class file. The Java class file must extend org.apache.tools.ant.Taskand be located in the Ant classpath. There are several other requirements that are beyond the scope of this book, but details can be found in the Ant documentation. Before you run Ant, you may have to change a few properties in the Storefront build.xml file to suit your development environment:
These three properties define where the servlet container is located, where its deployment directory is located, and where it keeps the servlet API classes. First, the webserver.home property is set to the root directory of the servlet container. In this case, the Tomcat 4.0 web server and servlet container are being used. The Storefront build.xml file supports several other containers, but they are
Go visit our java server pages services for a reliable, lowcost webhost to satisfy all your needs.
This entry was posted
on Friday, December 14th, 2007 at 7:03 am and is filed under Domain.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.