Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | == WOProject == | ||
| 2 | |||
| 3 | A suite of extensions for ant to build WOApplications and WOFrameworks | ||
| 4 | |||
| 5 | * [[WOProject Ant Tasks (old site)>>http://objectstyle.org/woproject-old/ant/]] | ||
| 6 | * [[Embedding WOFrameworks]] | ||
| 7 | Please see the link to the old site above until the core documentation is moved to this new wiki. | ||
| 8 | |||
| 9 | === Introduction === | ||
| 10 | |||
| 11 | Ant build files are broken into what are called 'targets', similar to a Makefile. These targets are a group of, what are called, 'tasks'. Tasks are used for getting work done; they make something happend directly, e.g. move files on the filesystem, compile java source files into classes, transfer files from one server to another over ssh, etc. | ||
| 12 | |||
| 13 | While Ant is distributed with around fifty built-in tasks, any number of customized tasks can easily be added by developers outside of the core Ant team. | ||
| 14 | |||
| 15 | WOProject is such a project. WOProject adds a half dozen tasks to Ant. These tasks allow WebObject developers the freedom to use Ant in their build process, instead of the using Apple's XCode suite. | ||
| 16 | |||
| 17 | Reasons for using Ant to build WebObjects frameworks and applications: | ||
| 18 | |||
| 19 | * Ant if highly configurable and flexible, with constant additions from the open source community, and is considered a defacto standard by the Java community | ||
| 20 | |||
| 21 | * Builds of project with a very large number of files without dependency failures | ||
| 22 | |||
| 23 | * Allows easy automation of daily builds for team of developers, i.e. nightly builds for smoke testing, etc. |