Java J2ee Planet

Introduction: This is an introductory tutorial to the Ant build tool, a free tool under GNU License and is available at http://jakarta.apache.org/ant/ . Ant allows the developer to automate the repeated process involved in the development of J2EE application. Developers can easily write the script to automate the build process like compilation, archiving and deployment. It is intended for people starting out with Ant and Java development, and aims to provide enough detail to get started.   What is Ant? Ant is a platform-independent scripting tool that lets you construct your build scripts in much the same fashion as the "make" tool in C or C++. You can use a large number of built-in tasks in Ant without any customization. Some of the most important tasks and related commands are built in the Ant distribution.

As part of our project we have to deliver the EARs to the client. Usually we use Ant script to run the build.xml file. But this when we are running build.xml using ant script, we have faced the following error. The RAD / Eclipse console is show the following message stating that ·          “build\build.xml:251: Problem: failed to create task or type projectBuild” ,“Cause: The name is undefined” ·          Action: Check the spelling ·          Action: Check that any custom tasks/types have been declared. ·          Action: Check that any <presetdef>/<macrodef> declarations have taken place. See the exact error that displayed on RAD/Eclipse console

Antmod is a Java and Ant based tool for:    1. Build Management:           * Speed-up java development with Antmod's plugins [...]           * Share build files across projects [...]    2. Release Management:           * Describe a project using release descriptors [...]           * Standardize versioning across projects [...]           * Modularize your software development process [...]    3. Repository Management:           * Manage your CVS or Subversion repository [...] Antmod's repository management, release descriptors, working with modules, Ant buildfiles and Ant build plugins make it a powerful and complete out-of-the-box solution for any software development project, esp...

Apache Ant is a Java-based build tool. In theory, it is kind of like Make, but without Make's wrinkles. Why another build tool when there is already make, gnumake, nmake, jam, and others? Because all those tools have limitations that Ant's original author couldn't live with when developing software across multiple platforms. Make-like tools are inherently shell-based -- they evaluate a set of dependencies, then execute commands not unlike what you would issue in a shell. This means that you can easily extend these tools by using or writing any program for the OS that you are working on. However, this also means that you limit yourself to the OS, or at least the OS type such as Unix, that you are working on. Makefiles are inherently evil as well. Anybody who has worked on them for any time has run into the dreaded tab problem. "Is my command not executing because I have a space in front of my tab!!!" said the original author of Ant way too many times. Tools lik...

How Do I: Call wlwBuild.cmd from an Ant build.xml file?   The following topic explains how to create an Ant task that calls the command line tool wlwBuild.cmd. wlwBuild.cmd is used to create application-level EAR files or project-level JAR files for deployment to a production server. To create an Ant build.xml file, you can either auto-generate a build.xml file or you can write the file by hand. To auto-generate an Ant build.xml file for the application 1.     Open the target application in WebLogic Workshop. 2.     From the Tools menu, select Application properties . 3.     In the Application Properties dialog, from the left-side navigation panel, select the Build node. 4.     In the section labeled Export , click the Export to Ant file button. 5.     An Ant file named exported_build.xml is generated and placed in the application's root directory, e.g., BEA_HOME/we...

WebLogic Workshop uses a standard Ant build process for all applications. You can create a custom Ant build file for an application that extends the standard build process or uses different build targets altogether. If you want to extend or modify the standard build process, you should first export the standard application build file and begin by modifying that file. To Export the Standard Application Build File 1.     Choose Tools --> Application Properties to display the Application Properties dialog. 2.     In the left-hand pane, select Build . 3.     In the Build Type pane, click Export to Ant File . A dialog appears informing that the exported_build.xml file has been stored in the root of the application folder. Click OK . The exported Ant file contains a set of standard tasks and targets for managing the build for your application. Note the class workshop.core.WlwBuildTask called by the "wlwBuild" task is the same class called by ...