Apache Ant

Ant is a Java library and command-line tool. Ant’s mission is to drive processes described in build files as targets and extension points dependent upon each other. The main known usage of Ant is the build of Java applications. Ant supplies a number of built-in tasks allowing to compile, assemble, test and run Java applications. Ant can also be used effectively to build non Java applications, for instance C or C++ applications. More generally, Ant can be used to pilot any type of process which can be described in terms of targets and tasks.

Ant is written in Java. Users of Ant can develop their own “antlibs” containing Ant tasks and types, and are offered a large number of ready-made commercial or open-source “antlibs”.

Ant is extremely flexible and does not impose coding conventions or directory layouts to the Java projects which adopt it as a build tool.

Software development projects looking for a solution combining build tool and dependency management can use Ant in combination with Ivy.

Tagged : / / / /

Introduction of Apache Ant

Apache Ant is a software tool for automating software build processes. It is similar to Make but is implemented using the Java language, requires the Java platform, and is best suited to building Java projects.

The most immediately noticeable difference between Ant and Make is that Ant uses XML to describe the build process and its dependencies, whereas Make has its Makefile format. By default the XML file is named build.xml.

Ant is an Apache project. It is open source software, and is released under the Apache Software License.

Tagged : / / / / / / / /

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 : / / / / / /

Java Command Line Options

-client       to select the “client” VM
-server       to select the “server” VM
-hotspot      is a synonym for the “client” VM  [deprecated]
The default VM is client.

-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
set a system property
enable verbose output
-version      print product version and exit
require the specified version to run
-showversion  print product version and continue
-jre-restrict-search | -jre-no-restrict-search
include/exclude user private JREs in the version search
-? -help      print this help message
-X            print help on non-standard options
enable assertions
disable assertions
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
load native agent library <libname>, e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
load native agent library by full pathname
load Java programming language agent, see java.lang.instrument
show splash screen with specified image

Tagged : / / /

Java.lang.NoClassDefFoundError: com/vladium/emma/rt/RT

rajeshkumar created the topic: “java.lang.NoClassDefFoundError: com/vladium/emma/rt/RT”

I got sometime following error while using emma…

“java.lang.NoClassDefFoundError: com/vladium/emma/rt/RT”

Solution can be found in…

Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Bundling Java Runtime Environments

deployexpert created the topic: Bundling Java Runtime Environments
Since InstallAnywhere installers are Java based, they require a Java Virtual Machine
(VM) to run. InstallAnywhere installers can bundle a virtual machine with the
installer, thus eliminating the possibility that the installer will not find a suitable
virtual machine for the product or for the installer.
Developers can choose whether or not the end-user will have a choice of VMs to use
for the installed product.
InstallAnywhere installers run from the bundled virtual machine. In order to bundle a
virtual machine, it must be packaged as a VM Pack. Free VM packs may be found on
the Macrovision Web site (details on how to create your own VM Packs can be found
A VM will not be installed under the following conditions:

Tagged :

Creating Launchers for Java Applications

deployexpert created the topic: Creating Launchers for Java Applications
InstallAnywhere provides an action that is available from the Install task which will
create launchers for Java applications. Click the Create Launcher button. This action
creates a platform-native executable for launching a Java application (also known as a
LAX executable). This LAX allows Java applications to be launched as if they were
platform-native (for example, the LaunchAnywhere executable can be launched by
double-clicking or by being called directly from the command line). A
LaunchAnywhere executable is also responsible for invoking the Java runtime, setting
the environment for the Java application, and passing any command line arguments
that may be required by the application.
When adding a LaunchAnywhere action you will be given the option to search for the
main class of your Java application. You can let InstallAnywhere find it for you, or you
can enter it yourself. You can also define the command line arguments that should to
be passed to your Java application when the LaunchAnywhere executable is run.
On Windows, InstallAnywhere will append .exe to the file. On Mac OS X, it will create
a .app package.
Defining the Launcher Type allows developers to specify whether the Java application
is either a GUI-based application calling javaw.exe (stdout and stderr suppressed by
default), or a console application calling java.exe (stdout and stderr directed to the
console by default). In addition, on Windows systems, console launchers will redirect
stdout and stderr output to the same console window from which they were invoked.
The Launcher Icon enables developers to select the icon to be used for the LAX
executable on the Mac OS X and Windows platforms. Custom icons are not available
on Unix installers. Mac OS X icons may be 128 x 128.

Tagged :

Any Possible Software/Plugin FoR SCM Workflow

pankaj2252369@gmail.com created the topic: Any possible Software/plugin for SCM workflow?
Hey Team, Thanks for lot of information on the site. wonderful work.

Any idea on SCM workflow software/framework ? which would help me to complete the SDLC lifecycle.

For E.g: When ever developers are done with their changes/check-ins, they would request CM team to build (via Email), And when CM builds and deploy , they will email to Testing Team, finally when its been tested they will let CM/RM team inform about the bugs, etc. finally product will be released.

All this was happening manually(via emails). If we have a workflow software, so that we can have everything in process oriented and SCM would be very easy.

Any Suggestion are welcome.

If know of any plug-ins , we can extend our programs to make it work to our systems.

Thanks in Advance!

rajeshkumar replied the topic: Re: Any possible Software/plugin for SCM workflow?
I would suggest following in Commercial | Opensource:-
SCM Workflow consisit of following..
SCM Tools |Scripting |Build / WorkFlow Mgmt Tools |
| Release / Dep Tools | Security | Testing Tools |
Test Coverage | Source-code Analysis | Issue Tracking Tools | IDEs Integration |Virtualization |

Please find list of tools and find you combination based in your project requirement and budget

Build / WorkFlow Mgmt Tools

Apache Continuum
OpenMake Meister
Team Foundation Server
Electric Cloud

SCM Tools

CA Harvest
MKS Source Integrity
Team Foundation Server


Shell Scripts
Perl Scripts
Visual Studio

Release / Dep Tools
Rational Team Concert


Active Directory
Single Sign-on

Testing Tools

Source-code Analysis


Issue Tracking Tools

HP Quality Center
PVCS Tracker
Team Foundation Server

IDEs Integration

Visual Studio


VMWare Lab Manager
Amazon (Elastic Cloud)
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

pankaj2252369@gmail.com replied the topic: Re: Any possible Software/plugin for SCM workflow?
Thanks for the response. But this i snot actually i am looking for.. I have idea on the mentioned tools. But wanted to create one separate tool for our internal purpose. So i am just checking, if there are any SCM related plugins /frame works in market, So that i do not spend more time on the things that are available.

Anyways.. Thank you so much!

rajeshkumar replied the topic: Re: Any possible Software/plugin for SCM workflow?
Hi John,

May be i am getting confused from you questions. Framework which can help you to develop your internal tools????

You mean you would like to develop your own tools, Then you might want to identify the technology first using which you want your development work get started. There are plenty of framework in Java| C++ | Perl | Pythin| Php | Ruby on rails etc
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged : / / / / /