Apache Ant: A Build Tool

Apache Ant (or simply Ant) is an XML-based build scripting language used heavily by the Open Source community. Ant automates tasks such as compiling source code, building deployment packages and automatically checking dependencies of what items need to be updated in a build set.

Tagged : / / /

Using Ant to build J2EE Applications

Apache Ant (Another Neat Tool) is a build tool, mainly for Java projects. A build tool can be used to automate certain repetitive tasks, e.g. compiling source code, running software tests, creating jar files, javadocs, etc.

A build process typically includes:

  • the compilation of the Java source code into Java bytecode
  • creation of the .jar file for the distribution of the code
  • creation of the Javadoc documentation

Ant uses a xml file for its configuration. This file is usually called “build.xml”. Within this build file you specify the targets for ant. A target is a step which ant will perform. You also can specific dependencies. If target A depends on target B, ant will first do B and then A. Also you specify the main target. This target is the target ant will try to execute per default. If this target depends on other targets then ant will automatically perform these task first and so on and so on.

Tagged : / / / / / /

Useful links for Sonar with Ant

rajeshkumar created the topic: Useful links for Sonar with Ant

Sonar with Ant

Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

rajeshkumar replied the topic: Re: Useful links for Sonar with Ant
Sonar and Other Quality Tools


Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Ant cpptask with ivy

rajeshkumar created the topic: ant cpptask with ivy
A company I am working for, has some c binaries build with ant using cpptask. They use ivy to retrieve shared c libraries every time we start a build which wastes a significant amount of time comparing the revisions and downloading, when then only need to be download if the header files have changed. I have added a target which sets a var, which causes the build to skip over the ivy steps but I’d like a better solution. I see that cpptask creates a file history.xml and only rebuilds to binary if any of the sources have change. I’d like to know if there is way to independently test if the binary needs to build, and it does, I’d like it fire off the ivy targets. I’d also like for a variable to be set if the binary was rebuilt so that I can conditionally start an rpm generation task


Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Ant+Unable to create directory as a file already

rajeshkumar created the topic: Ant+Unable to create directory as a file already

I have one file called djir.ear and I am trying to create a folder with the same name “jir.ear” same location using ant script.
but i get error message saying that
Unable to create directory as a file alr
eady exists with that name

Can you suggest me any solution for this? as i build is failing and mkdir do not support failonerror propertry 🙁
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Help in copy files from list using ant

scmuser created the topic: Help in copy files from list using ant
Help in copy files from list using ant


I have one file called list.txt where i have mentioned all the files which need to be copied from specific directry.

can you please help me with the right copy task syntax which read the files name from list.txt and copy to destination directory???

tpatil replied the topic: Re:Help in copy files from list using ant
You can “for” loop in build to achieve this

Copying File @{val}


rajeshkumar replied the topic: Re:Help in copy files from list using ant
I would recommend following command for same…

Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

scmuser replied the topic: Re:Help in copy files from list using ant

amitanand123 replied the topic: Re:Help in copy files from list using ant

Tagged :

Ant Scripting Issue

ant-qa created the topic: Ant Scripting Issue
1) I have many ant build files ( .xml files / test scripts) in folder : bin/execute

2) I have another testsuit.xml file (ant build file) that works as a test suit. All the test cases in folder : bin/execute are executed in the order they appear in testsuit.xml

3) I want to write code maybe another ant test (.xml file) to make sure that all the test cases are added (executed) in the test suit.

4) Test cases in the testsuit.xml can be identified by :

Any thoughts will be extremely appreciated


Tagged :

Condition with Task in Ant

scmuser created the topic: Condition with Task in Ant

How can i use conditions in Ant Task execution?

Any idea?

tpatil replied the topic: Re: Condition with Task in Ant


rajeshkumar replied the topic: Re: Condition with Task in Ant

I guess questions was based on applying condition for Aant TASK instead of Ant Target. Following ways i mean using you can set the conditional properties value but set condition with TASK.

There is one external lib ant-contrib which can be used to put conditional Task such you can find more details in links below…..
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

ANT Build Integration with InstallAnywhere

installanywhereExpert created the topic: ANT Build Integration with InstallAnywhere
ANT Build Integration with InstallAnywhere

ANT is a powerful, Java based build tool developed by the Apache Foundation’s Jakarta Project. It can be used to control complex build tasks in Java and other development environments. ANT manages specific actions though “tasks” which can either be part of the core ANT distribution or available as extensions. InstallAnywhere comes with an ANT task to build installers from ANT. The InstallAnywhere ANT task is located in your InstallAnywhere application folder, inside “resource” and then inside “/build”.. Add “iaant.jar” to your classpath when executing ANT to get access to the InstallAnywhere ANT task. ANT uses an XML file to specify the order of tasks for your build process. More information on ANT can be found on the Apache Foundation’s Jakarta Project Web site.

Task Name and Class
The InstallAnywhere ANT task is specified as follows:

This task can be found inside the iaant.jar file, in your InstallAnywhere application
folder, inside “resource” and then inside “build”.

After defining the task, specify any parameter necessary for the build settings:

Replace the IAlocation with the absolute path to your own InstallAnywhere
application folder. If InstallAnywhere cannot be found, ANT will search for it in one of
the default locations or look in the registry to find where InstallAnywhere was
installed to.
Specify the path and file name of the project to build in the IAProjectFile parameter.
All other properties are optional. The parameters closely match the properties found
in the Build Properties File described above. The following table shows the available

ashok423 replied the topic: Re: ANT Build Integration with InstallAnywhere
Hi, The parameters table which you mentioned is missing from the post. Can you please post it again.

Tagged : /

Top 10 DevOps Tools which is mostly used by DevOps Engineers | scmGalaxy

DevOps is an important component for software industry today. Developing and implementing a DevOps culture helps to focus IT results and to save time and money as the gap between developers and IT operations teams closes. Just as the term and culture are new, so are many of the best DevOps tools these DevOps engineers use to do their jobs efficiently and productively. To help you in your DevOps process, we have searched and created this list of DevOps tools which is mostly used by DevOps Engineers in their projects.

1. Chef


Chef is an extremely popular tool among DevOps engineers. From IT automation to configuration management, Chef relies on recipes and resources so you can manage unique configurations and feel secure knowing Chef is checking your nodes and bringing them up to date for you.
Key Features:
  • Manage nodes from a single server
  • Cross-platform management for Linux, Windows, Mac OS, and more
  • Integrates with major cloud providers
  • Premium features available

2. Jenkins



An extensible continuous integration engine, Jenkins is a top tool for DevOps engineers who want to monitor executions of repeated jobs. With Jenkins, DevOps engineers have an easier time integrating changes to projects and have access to outputs to easily notice when something goes wrong.
Key Features:
  • Permanent links
  • RSS/email/IM integration
  • After-the-fact tagging
  • JUnit/TestNG test reporting
  • Distributed builds
3. Puppet


Puppet is an open-source configuration management tool. It runs on many Unix-like systems as well as on Microsoft Windows, and includes its own declarative language to describe system configuration. DevOps engineers often rely on Puppet for IT automation. Get a handle on configuration management and software while making rapid, repeatable changes with Puppet.
Key Features:
  • Automatically enforce consistency of environments
  • Works across physical and virtual machines
  • A common tool-chain
  • Support key DevOps best practices, including continuous delivery

4. Ant



A Java library and command-line tool, Apache Ant looks “to drive processes described in build files as targets and extension points dependent upon each other.” This build automation tool is one that saves DevOps engineers a great deal of time.
Key Features:
  • Supplies a number of built-in tasks for compiling, assembling, testing, and running Java applications
  • Builds non-Java applications, such as C or C++ applications
  • Pilot any type of process which can be described in terms of targets and tasks
  • Extremely flexible and does not impose coding conventions or directory layouts to the Java projects which adopt it as a build tool

5. Apache Maven


DevOps engineers can manage a project’s build, reporting, and documentation from a central piece of information with Apache Maven. A software project management and comprehension tool, Maven has been a reliable tool for DevOps engineers.
Key Features:
  • Simple project setup follows best practices
  • Easily work with multiple projects at one time
  • Large repository of libraries and metadata that continue to grow
  • Extensible, with the ability to write plugins in Java or scripting languages
6. Logstash


For open source log processing, search, and analytics, Logstash is a popular tool among DevOps engineers. Because Logstash is licensed under Apache 2.0, you can use it in the way that best suits your needs.

Key Features:
  • Collects, parses, and stores logs for later use
  • Includes a web interface for searching and drilling into all of your logs
  • Ship logs from any source, parse them, timestamp them correctly, index them, and search them

7. Docker



An open platform for distributed applications, Docker is an application for DevOps engineers who want to “build, ship, and run any app, anywhere.” With Docker, you can quickly assemble apps from components and work collaboratively.
Key Features:
  • Assemble multi-container apps and run on any infrastructure
  • Compose an app using both proprietary containers and Docker Hub Official Repos
  • Manage all containers of an app as a single group
  • Cluster an app’s containers to optimize resources and provide high-availability
8. New Relic


With New Relic APM, DevOps engineers spend less time monitoring applications and more time on building and deploying. A popular, reliable tool, New Relic APM is a great choice for DevOps engineers.
Key Features:
  • Helps in the build, deployment, and maintenance of web software
  • Application monitoring in one place
  • Cross application and transaction tracing
  • Database and availability and error monitoring
9. Gradle



Gradle is a robust tool for automating building, testing, publishing, and deploying software packages and other projects. With the combined power and flexibility of Ant and Maven, Gradle is an open source build automation system which is perfect and very useful for DevOps engineers.
Key Features:
  • Declarative builds and build-by-convention
  • Language for dependency-based programming
  • Structure your build
  • Deep API
  • Multi-project builds
  • Ease of migration
10. Git 



Git is a mature, actively maintained open source project originally developed in 2005 by Linus Torvalds, the famous creator of the Linux operating system kernel. Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
Key Features:
  • Working offline
  • Fast to Work With
  • Repositories Are Smaller
  • Moving or Adding files
  • Ignore Certain Files
  • Branches
  • Check the Status of Your Changes
  • Stash Branches
  • Cherry Pick Changes from Branches
  • Find version that Introduced a bug using Binary Search
These are the most popular DevOps tools which are used by DevOps engineers or practitioners these days. But to make most out of these tools you need to have proper knowledge of these tools like installation process, implementation process, where to you use, how to use, troubleshooting and much more. So, if you think you need help or training for these tools or for DevOps related helps than we are here to assist you with our industry expertise professionals.
Tagged : / / / / / / / / / / / / / / / / / / / /