Im trying to install ant in order to use it with Tomcat (first time Im
using them)Tomcat installed fine but with ant I followed the
instructions until I got stuck on this one, which does not work:
"....Your are now ready to build Ant:
build -Ddist.dir=<directory_to_contain_Ant_distribution> dist
(Windows)
This will create a binary distribution of Ant in the directory you
specified...."
My system tells me That "build" is not recognized as a program or
instruction.
Somewhere I saw that probably "ant build" before will make it work but
it doesn´t, but I´ll check it for a while again and try to find my
error.
-----Mensaje original-----
De: Bill Chmura [mailto:Bill@Explosivo.com]
Enviado el: Jueves, 12 de Junio de 2003 11:30 p.m.
Para: 'Ant Users List'
Asunto: RE: Error setting up ant
What are you trying to do?
Build.xml is something you create for the specific project you are
working on. For example if you have two different programs you are
developing you would have two different build.xml files.
Are you trying to compile tomcat? I am not sure what you are trying to
accomplish with ant
-----Original Message-----
From: Juan Carlos Salazar [mailto:jc.salazar@terra.com.mx]
Sent: Friday, June 13, 2003 12:01 AM
To: 'Ant Users List'
Subject: RE: Error setting up ant
First of all...thanks a lot (muchas gracias).
I do have a build.xml in my ant directory which I copied from the Tomcat
Directory (because Ant did not came up with a file with this name), is
that wrong??
Now checking into the file which I have in the C:\Ant\build.xml I do
have this line:
<project name="My Project" default="compile" basedir=".">
(I'm guessing that basedir has to be changed...maybe to c:\ant or
C:\Ant\apache-ant-1.5.3-1 ?)
but I do not have a <target name="build".. > Do I just make one up??
PD: I'm sorry for all this basic questions I'm an Industrial Engineering
trying to figure this out..
This is my build.xml, Do I have to keep working to change some things or
this is a completely wrong build file?:
<!--
General purpose build script for web applications and web services,
including enhanced support for deploying directly to a Tomcat 4
based server.
This build script assumes that the source code of your web
application
is organized into the following subdirectories underneath the
source
code directory from which you execute the build script:
docs Static documentation files to be copied to
the "docs" subdirectory of your
distribution.
src Java source code (and associated resource
files)
to be compiled to the "WEB-INF/classes"
subdirectory of your web applicaiton.
web Static HTML, JSP, and other content (such
as
image files), including the WEB-INF
subdirectory
and its configuration file contents.
$Id: build.xml.txt,v 1.7 2002/12/28 09:08:58 jfclere Exp $
-->
<!-- A "project" describes a set of targets that may be requested
when Ant is executed. The "default" attribute defines the
target which is executed if no specific target is requested,
and the "basedir" attribute defines the current working directory
from which Ant executes the requested task. This is normally
set to the current working directory.
-->
<project name="My Project" default="compile" basedir=".">
<!-- ===================== Property Definitions
=========================== -->
<!--
Each of the following properties are used in the build script.
Values for these properties are set by the first place they are
defined, from the following list:
* Definitions on the "ant" command line (ant -Dfoo=bar compile).
* Definitions from a "build.properties" file in the top level
source directory of this application.
* Definitions from a "build.properties" file in the developer's
home directory.
* Default definitions in this build.xml file.
You will note below that property values can be composed based on the
contents of previously defined properties. This is a powerful
technique
that helps you minimize the number of changes required when your
development
environment is modified. Note that property composition is allowed
within
"build.properties" files as well as in the "build.xml" script.
-->
<property file="build.properties"/>
<property file="${user.home}/build.properties"/>
<!-- ==================== File and Directory Names
======================== -->
<!--
These properties generally define file and directory names (or paths)
that
affect where the build process stores its outputs.
app.name Base name of this application, used to
construct filenames and directories.
Defaults to "myapp".
app.path Context path to which this application should be
deployed (defaults to "/" plus the value of the
"app.name" property).
app.version Version number of this iteration of the
application.
build.home The directory into which the "prepare" and
"compile" targets will generate their output.
Defaults to "build".
catalina.home The directory in which you have installed
a binary distribution of Tomcat 4. This will
be used by the "deploy" target.
dist.home The name of the base directory in which
distribution files are created.
Defaults to "dist".
manager.password The login password of a user that is assigned the
"manager" role (so that he or she can execute
commands via the "/manager" web application)
manager.url The URL of the "/manager" web application on the
Tomcat installation to which we will deploy web
applications and web services.
manager.username The login username of a user that is assigned the
"manager" role (so that he or she can execute
commands via the "/manager" web application)
-->
<property name="app.name" value="myapp"/>
<property name="app.path" value="/${app.name}"/>
<property name="app.version" value="0.1-dev"/>
<property name="build.home" value="${basedir}/build"/>
<property name="catalina.home" value="C:\Tomcat 4.1\bin"/> <!-- UPDATE
THIS! -->
<property name="dist.home" value="${basedir}/dist"/>
<property name="docs.home" value="${basedir}/docs"/>
<property name="manager.url" value="http://localhost:8080/manager"/>
<property name="src.home" value="${basedir}/src"/>
<property name="web.home" value="${basedir}/web"/>
<!-- ================== Custom Ant Task Definitions
======================= -->
<!--
These properties define custom tasks for the Ant build tool that
interact
with the "/manager" web application installed with Tomcat 4. Before
they
can be successfully utilized, you must perform the following steps:
- Copy the file "server/lib/catalina-ant.jar" from your Tomcat 4
installation into the "lib" directory of your Ant installation.
- Create a "build.properties" file in your application's top-level
source directory (or your user login home directory) that defines
appropriate values for the "manager.password", "manager.url", and
"manager.username" properties described above.
For more information about the Manager web application, and the
functionality
of these tasks, see
<http://localhost:8080/tomcat-docs/manager-howto.html>.
-->
<taskdef name="install"
classname="org.apache.catalina.ant.InstallTask"/>
<taskdef name="list" classname="org.apache.catalina.ant.ListTask"/>
<taskdef name="reload"
classname="org.apache.catalina.ant.ReloadTask"/>
<taskdef name="remove"
classname="org.apache.catalina.ant.RemoveTask"/>
<!-- ==================== Compilation Control Options
==================== -->
<!--
These properties control option settings on the Javac compiler when it
is invoked using the <javac> task.
compile.debug Should compilation include the debug option?
compile.deprecation Should compilation include the deprecation
option?
compile.optimize Should compilation include the optimize option?
-->
<property name="compile.debug" value="true"/>
<property name="compile.deprecation" value="false"/>
<property name="compile.optimize" value="true"/>
<!-- ==================== External Dependencies
=========================== -->
<!--
Use property values to define the locations of external JAR files on
which
your application will depend. In general, these values will be used
for
two purposes:
* Inclusion on the classpath that is passed to the Javac compiler
* Being copied into the "/WEB-INF/lib" directory during execution
of the "deploy" target.
Because we will automatically include all of the Java classes that
Tomcat 4
exposes to web applications, we will not need to explicitly list any
of those
dependencies. You only need to worry about external dependencies for
JAR
files that you are going to include inside your "/WEB-INF/lib"
directory.
-->
<!-- Dummy external dependency -->
<!--
<property name="foo.jar"
value="/path/to/foo.jar"/>
-->
<!-- ==================== Compilation Classpath
=========================== -->
<!--
Rather than relying on the CLASSPATH environment variable, Ant
includes
features that makes it easy to dynamically construct the classpath you
need for each compilation. The example below constructs the compile
classpath to include the servlet.jar file, as well as the other
components
that Tomcat makes available to web applications automatically, plus
anything
that you explicitly added.
-->
<path id="compile.classpath">
<!-- Include all JAR files that will be included in /WEB-INF/lib -->
<!-- *** CUSTOMIZE HERE AS REQUIRED BY YOUR APPLICATION *** -->
<!--
<pathelement location="${foo.jar}"/>
-->
<!-- Include all elements that Tomcat exposes to applications -->
<pathelement location="${catalina.home}/common/classes"/>
<fileset dir="${catalina.home}/common/endorsed">
<include name="*.jar"/>
</fileset>
<fileset dir="${catalina.home}/common/lib">
<include name="*.jar"/>
</fileset>
<pathelement location="${catalina.home}/shared/classes"/>
<fileset dir="${catalina.home}/shared/lib">
<include name="*.jar"/>
</fileset>
</path>
<!-- ==================== All Target
====================================== -->
<!--
The "all" target is a shortcut for running the "clean" target followed
by the "compile" target, to force a complete recompile.
-->
<target name="all" depends="clean,compile"
description="Clean build and dist directories, then compile"/>
<!-- ==================== Clean Target
==================================== -->
<!--
The "clean" target deletes any previous "build" and "dist" directory,
so that you can be ensured the application can be built from scratch.
-->
<target name="clean"
description="Delete old build and dist directories">
<delete dir="${build.home}"/>
<delete dir="${dist.home}"/>
</target>
<!-- ==================== Compile Target
================================== -->
<!--
The "compile" target transforms source files (from your "src"
directory)
into object files in the appropriate location in the build directory.
This example assumes that you will be including your classes in an
unpacked directory hierarchy under "/WEB-INF/classes".
-->
<target name="compile" depends="prepare"
description="Compile Java sources">
<!-- Compile Java classes as necessary -->
<mkdir dir="${build.home}/WEB-INF/classes"/>
<javac srcdir="${src.home}"
destdir="${build.home}/WEB-INF/classes"
debug="${compile.debug}"
deprecation="${compile.deprecation}"
optimize="${compile.optimize}">
<classpath refid="compile.classpath"/>
</javac>
<!-- Copy application resources -->
<copy todir="${build.home}/WEB-INF/classes">
<fileset dir="${src.home}" excludes="**/*.java"/>
</copy>
</target>
<!-- ==================== Dist Target
===================================== -->
<!--
The "dist" target creates a binary distribution of your application
in a directory structure ready to be archived in a tar.gz or zip file.
Note that this target depends on two others:
* "compile" so that the entire web application (including external
dependencies) will have been assembled
* "javadoc" so that the application Javadocs will have been created
-->
<target name="dist" depends="compile,javadoc"
description="Create binary distribution">
<!-- Copy documentation subdirectories -->
<mkdir dir="${dist.home}/docs"/>
<copy todir="${dist.home}/docs">
<fileset dir="${docs.home}"/>
</copy>
<!-- Create application JAR file -->
<jar jarfile="${dist.home}/${app.name}-${app.version}.war"
basedir="${build.home}"/>
<!-- Copy additional files to ${dist.home} as necessary -->
</target>
<!-- ==================== Install Target
================================== -->
<!--
The "install" target tells the specified Tomcat 4 installation to
dynamically
install this web application and make it available for execution. It
does
*not* cause the existence of this web application to be remembered
across
Tomcat restarts; if you restart the server, you will need to
re-install all
this web application.
If you have already installed this application, and simply want Tomcat
to
recognize that you have updated Java classes (or the web.xml file),
use the
"reload" target instead.
NOTE: This target will only succeed if it is run from the same server
that
Tomcat is running on.
NOTE: This is the logical opposite of the "remove" target.
-->
<target name="install" depends="compile"
description="Install application to servlet container">
<install url="${manager.url}"
username="${manager.username}"
password="${manager.password}"
path="${app.path}"
war="file://${build.home}"/>
</target>
<!-- ==================== Javadoc Target
================================== -->
<!--
The "javadoc" target creates Javadoc API documentation for the Java
classes included in your application. Normally, this is only required
when preparing a distribution release, but is available as a separate
target in case the developer wants to create Javadocs independently.
-->
<target name="javadoc" depends="compile"
description="Create Javadoc API documentation">
<mkdir dir="${dist.home}/docs/api"/>
<javadoc sourcepath="${src.home}"
destdir="${dist.home}/docs/api"
packagenames="*">
<classpath refid="compile.classpath"/>
</javadoc>
</target>
<!-- ====================== List Target
=================================== -->
<!--
The "list" target asks the specified Tomcat 4 installation to list the
currently running web applications, either loaded at startup time or
installed dynamically. It is useful to determine whether or not the
application you are currently developing has been installed.
-->
<target name="list"
description="List installed applications on servlet container">
<list url="${manager.url}"
username="${manager.username}"
password="${manager.password}"/>
</target>
<!-- ==================== Prepare Target
================================== -->
<!--
The "prepare" target is used to create the "build" destination
directory,
and copy the static contents of your web application to it. If you
need
to copy static files from external dependencies, you can customize the
contents of this task.
Normally, this task is executed indirectly when needed.
-->
<target name="prepare">
<!-- Create build directories as needed -->
<mkdir dir="${build.home}"/>
<mkdir dir="${build.home}/WEB-INF"/>
<mkdir dir="${build.home}/WEB-INF/classes"/>
<!-- Copy static content of this web application -->
<copy todir="${build.home}">
<fileset dir="${web.home}"/>
</copy>
<!-- Copy external dependencies as required -->
<!-- *** CUSTOMIZE HERE AS REQUIRED BY YOUR APPLICATION *** -->
<mkdir dir="${build.home}/WEB-INF/lib"/>
<!--
<copy todir="${build.home}/WEB-INF/lib" file="${foo.jar}"/>
-->
<!-- Copy static files from external dependencies as needed -->
<!-- *** CUSTOMIZE HERE AS REQUIRED BY YOUR APPLICATION *** -->
</target>
<!-- ==================== Reload Target
=================================== -->
<!--
The "reload" target tells the specified Tomcat 4 installation to
dynamically
reload this web application, to reflect changes in the underlying
classes or
the "web.xml" deployment descriptor.
-->
<target name="reload" depends="compile"
description="Reload application on servlet container">
<reload url="${manager.url}"
username="${manager.username}"
password="${manager.password}"
path="${app.path}"/>
</target>
<!-- ==================== Remove Target
=================================== -->
<!--
The "remove" target tells the specified Tomcat 4 installation to
dynamically
remove this web application from service.
NOTE: This is the logical opposite of the "install" target.
-->
<target name="remove"
description="Remove application on servlet container">
<remove url="${manager.url}"
username="${manager.username}"
password="${manager.password}"
path="${app.path}"/>
</target>
</project>
-----Mensaje original-----
De: Bill Chmura [mailto:Bill@Explosivo.com]
Enviado el: Jueves, 12 de Junio de 2003 08:54 a.m.
Para: 'Ant Users List'
Asunto: RE: Error setting up ant
He actually changes to the C:\ANT directory before executing...
Do you actually have a build.xml file in your ant directory?
-----Original Message-----
From: Jan.Materne@rzf.fin-nrw.de [mailto:Jan.Materne@rzf.fin-nrw.de]
Sent: Thursday, June 12, 2003 1:13 AM
To: user@ant.apache.org
Subject: AW: Error setting up ant
In the directory "C:\Documents and Settings\Carlos" there is a file
"build.xml" - the Ant buildfile. Somewhere at the beginning there is a
line
<project ... default="build" >
The default-clause let Ant execute the target "build" if don´t specify
one. And it seems that the buildfile hasn´t a target named "build"
<target name="build" ... >
Jan
> -----Ursprüngliche Nachricht-----
> Von: Bill Chmura [mailto:Bill@Explosivo.com]
> Gesendet am: Donnerstag, 12. Juni 2003 05:11
> An: 'Ant Users List'
> Betreff: RE: Error setting up ant
>
> Do you have a target named build in the build.xml file?
>
> Ant will automatically pick out a file named build.xml in the
> directory
>
> Calling ant build will run a target ( <target name="build"> ) in your
> build.xml file.
>
>
> -----Original Message-----
> From: Juan Carlos Salazar [mailto:jc.salazar@terra.com.mx]
> Sent: Wednesday, June 11, 2003 7:20 PM
> To: 'Ant Users List'
> Subject: Error setting up ant
>
>
> Hopefully somebody can help me with this its been 3 days and i can´t
> get thru, Thx for any hint:
>
> The following error displays when Im trying to run ant:
>
> Microsoft Windows XP [Versión 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\Documents and Settings\Carlos>cd c:\ant
>
> C:\Ant>ant build
> Buildfile: build.xml
>
> BUILD FAILED
> Target `build' does not exist in this project.
>
> Total time: 1 second
> C:\Ant>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.459 / Virus Database: 258 - Release Date: 25/02/2003
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.459 / Virus Database: 258 - Release Date: 25/02/2003
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.459 / Virus Database: 258 - Release Date: 25/02/2003
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.459 / Virus Database: 258 - Release Date: 25/02/2003
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.459 / Virus Database: 258 - Release Date: 25/02/2003
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
|