Flylib.com

Books Software

 
 
 

Conventions Used in This Book


Conventions Used in This Book

There are some conventions I'll use that you should know about. When there's a new piece of code under discussion, it will appear highlighted; when there's more code to come, you'll see three dots. Here's what that looks like:

import org.apache.tools.ant.Task;
import org.apache.tools.ant.BuildException;

public class Project extends Task 
{
    private String language;

    public void execute( ) throws BuildException 
    {
        System.out.println("The language is " + language);
    }

public void setLanguage(String language)


{


this.language = language;

.
        .
        .

}

}

Note that I'll use the standard convention for selecting menu items in this book when menu items come into play (as when we use Ant in the Eclipse IDE). For instance, to create a new project in Eclipse, you use the File New Project menu item.

The following typographical conventions are used in this book:


Plain text

Indicates menu titles, menu options, menu buttons , and keyboard accelerators.


Italic

Indicates new terms, URLs, email addresses, filenames, file extensions, pathnames, directories, and Unix utilities.


Constant width

Indicates commands, options, switches, variables , types, classes, namespaces, methods , modules, properties, parameters, values, objects, events, event handlers, or XML tags.


Constant width italic

Shows text that should be replaced with user -supplied values.



Constant width bold

 

This icon signifies a tip, suggestion, or general note.


This icon signifies a caution or warning.



What You'll Need

All the software you'll need in this book can be downloaded from the Internet for free. You'll need Antthis book was written using Ant 1.6.1and I'll discuss where to get Ant in Chapter 1. Other software packages are used at various points in the book, such as the AntHill build server or the Eclipse IDE (Chapter 11 is on using Ant in Eclipse), and I'll show where to download all the requisite software as it's needed. It's all free.


Using Code Examples

This book is here to help you get your job done. In general, you may use the code in this book in your programs and documentation. You do not need to contact O'Reilly for permission unless you're reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from O'Reilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your product's documentation does require permission.

We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN. For example: " Ant: The Definitive Guide , Second Edition by Steve Holzner. Copyright 2005 O'Reilly Media, Inc., 0-596-00609-8."

If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at permissions@oreilly.com.


We'd Like to Hear from You

Please address comments and questions concerning this book to the publisher:

O'Reilly Media, Inc.
1005 Gravenstein Highway North
Sebastopol, CA 95472
(800) 998-9938 (in the United States or Canada)
(707) 829-0515 (international or local)
(707) 829-0104 (fax)

O'Reilly maintains a web page for this book, which lists errata, examples, and any additional information. You can access this page at:

">http://www.oreilly.com/catalog/<BOOK>

To comment or ask technical questions about this book, send email to:

bookquestions@oreilly.com

For more information about our books, conferences, Resource Centers, and the O'Reilly Network, see the following web site:

http://www.oreilly.com