Note that DOS descended file systems are case insensitive (apart from -the obscure aberration of the WinNT posix subsystem run against NTFS), +the obscure aberration of the WinNT POSIX subsystem run against NTFS), and that Windows pretends that all file extensions with four or more letters are also three letter extensions (try DELETE *.jav in your java directories to see a disastrous example of this). @@ -351,7 +351,7 @@ distributions, and is a simple download for . A Perl file with .pl extension, with the usual Unix path to perl on the line 1 comment and marked as executable can be run on Windows, OS/2 and Unix and hence called from Ant without issues. The -perl code can be left to resolve its own platform issues. Dont forget to +perl code can be left to resolve its own platform issues. Don't forget to set the line endings of the file to the appropriate platform when you redistribute Perl code; <fixCRLF> @@ -493,7 +493,7 @@ The project contains sub directories
Javadoc output can be @@ -555,7 +555,7 @@ an automated, continuous, background build process. Tightly coupled projects have all the source in the same tree; different projects own different subdirectories. Build files can be moved down to -those subdirectores (say src/com/iseran/core and src/com/iseran/extras), +those subdirectories (say src/com/iseran/core and src/com/iseran/extras), or kept at the top -with independent build files named core.xml and extras.xml @@ -597,7 +597,7 @@ can be still be built. The most aggressive strategy is to get a weekly or daily snapshot of the ant source, build it up and use it. This forces you to tweak the -build.xml files more regulary, as new tasks and attributes can take +build.xml files more regularly, as new tasks and attributes can take while to stabilise. You really have to want the new features, enjoy gratuitous extra work or take pleasure in upsetting your colleagues to take this approach. @@ -606,7 +606,7 @@ take this approach. Once you start extending Ant with new tasks, it suddenly becomes much more tempting to pull down regular builds. The most recent Ant builds -are invariably the the best platform for writing your extensions, as you +are invariably the best platform for writing your extensions, as you can take advantage of the regular enhancements to the foundational classes. It also prevents you from wasting time working on something which has already been done. A newly submitted task to do something @@ -727,7 +727,7 @@ Use Property Files Use external property files to keep per-user settings out the build files -especially passwords. Property files can also be used to dynamically set a number of properties based on the value of a single -property, simply by dyamically generating the property filename from the +property, simply by dynamically generating the property filename from the source property. They can also be used as a source of constants across multiple build files. @@ -805,8 +805,8 @@ be called from any of your main build files, perhaps with subtly changed parameters. Indeed, after a couple of projects you may be able to create a re-usable core build file which contains the core targets of a basic Java development project -compile, debug, deploy- which project specific -build files call with their own settings. If you can achive this then -you are definately making your way up the software maturity ladder. With +build files call with their own settings. If you can achieve this then +you are definitely making your way up the software maturity ladder. With a bit of work you may progress from being a SEI CMM Level 0 organisation "Individual Heroics are not enough" to SEI CMM Level 1, "Projects only succeed due to individual heroics" @@ -936,7 +936,7 @@ should contain a number of top level targets
Copyright © 2000-2003 Apache Software Foundation. All rights +
Copyright © 2000-2004 The Apache Software Foundation. All rights Reserved.