Where is build.xml

Asked 12 years, 1 month ago. Active 3 years, 6 months ago. Viewed 77k times. What is the file build. Improve this question.

Kellen Stuart 5, 3 3 gold badges 43 43 silver badges 63 63 bronze badges. Granit Granit 3 3 gold badges 12 12 silver badges 22 22 bronze badges. Add a comment.

Active Oldest Votes. Improve this answer. Where is the file located? Targets contain task elements. Each task element of the buildfile can have an id attribute and can later be referred to by the value supplied to this. The value has to be unique. For additional information, see the Tasks section below. Each project defines one or more targets. A target is a set of tasks you want to be executed. When starting Ant, you can select which target s you want to have executed. When no target is given, the project's default is used.

A target can depend on other targets. You might have a target for compiling, for example, and a target for creating a distributable. You can only build a distributable when you have compiled first, so the distribute target depends on the compile target. Ant resolves these dependencies.

It should be noted, however, that Ant's depends attribute only specifies the order in which targets should be executed—it does not affect whether the target that specifies the dependency s gets executed if the dependent target s did not need to run.

A task can have multiple attributes or arguments, if you prefer. The value of an attribute might contain references to a property. These references will be resolved before the task is executed. There is a set of built-in tasks , but it is also very easy to write your own.

All tasks can have a name attribute. Note that there should be no blank line s or whitespace s before the xml declaration. The default target for the build script. A project may contain any number of targets. This attribute specifies which target should be considered as the default. A target is a collection of tasks that you want to run as one unit.

In our example, we have a simple target to provide an informational message to the user. Table rpcservices Attributes. If the basepath attribute of the wsgen element is set, this attribute specifies the URI of the Enterprise Application module that corresponds to an EJB archive contained by the Enterprise Application archive.

Only if the basepath attribute of the wsgen element is set. Only if the basepath attribute of the wsgen element is not set. Table rpcservice Attributes. This name corresponds to the ejb-name element in the ejb-jar.

The path to the EJB archive is specified in the parent rpcservices element. The messageservices element is a container for any number of messageservice sub-elements. The messageservice element describes a specific message-style Web service by specifying a JMS destination that will receive or send messages. Table messageservice Attributes. Specifies whether the client that invokes this message-style Web service sends or receives messages to or from the JMS destination.

Specify send if the client sends messages to the JMS destination and receive if the client receives messages from the JMS destination. For example, the URL that accesses the first message-style Web service in the example in Example of a build.