diff --git a/docs/manual/CoreTasks/libraries.html b/docs/manual/CoreTasks/libraries.html index 7c3e1baf8..e91104a62 100644 --- a/docs/manual/CoreTasks/libraries.html +++ b/docs/manual/CoreTasks/libraries.html @@ -21,11 +21,11 @@ This task can:

    -
  1. Download publicly published JAR files by version.
  2. +
  3. Download publicly published JAR files by version
  4. Download JAR files from private file: or http: repositories
  5. Cache the JAR files in a directory tree
  6. Check for updates on a regular schedule
  7. -
  8. Build paths for compilation/execution.
  9. +
  10. Build paths for compilation/execution
  11. Fail the build if needed libraries are missing
  12. Force an update of all libraries
  13. Skip all downloading when offline @@ -90,7 +90,7 @@ property ant.maven.repository.dir to a new location.

    library

    -This is the core of the system; a library to (potentially) download. +This is the core of the system: a library to (potentially) download. @@ -140,8 +140,8 @@ This is the core of the system; a library to (potentially) download.

    Repository

    -A repository is Ant datatype that extends the Repository type. -Ant only ships with one: the mavenrepository. If no repository is +A repository is an Ant datatype that extends the Repository +type. Ant only ships with one: the mavenrepository. If no repository is declared inline, and no repositoryref attribute set, the task will default to the maven repository.

    @@ -241,9 +241,8 @@ situation is left to the experimentor, though reading the source will help.

    -Developers may add new polices (such -as signing incoming files) by adding new datatypes extending the -LibraryPolicy class.

    +Developers may add new policies (such as signing incoming files) by adding +new datatypes extending the LibraryPolicy class.

    noupdate

    @@ -253,7 +252,7 @@ equivalent of the offline flag.

    Example:

    -    <noupdate  />
    +    <noupdate />
     

    forceupdate

    @@ -262,7 +261,7 @@ equivalent of the offline flag.

    the build will halt.

    Example:

    -    <forceupdate  />
    +    <forceupdate />
     

    timestamp

    @@ -273,7 +272,7 @@ It is equivalent to setting the useTimestamp flag.

    Example:

    -    <timestamp  />
    +    <timestamp />
     

    scheduledupdate

    @@ -322,7 +321,7 @@ passed, or the set of files to check has to have changed.

    Example:

    -    <scheduledupdate days="1" hours="3" minutes="17"  />
    +    <scheduledupdate days="1" hours="3" minutes="17" />
     

    Check for an update every 27 hours, 17 minutes.

    @@ -357,7 +356,7 @@ expected.

    Example:

    -    <assertdownloaded cound="4"  />
    +    <assertdownloaded count="4" />
     

    Examples

    @@ -391,8 +390,7 @@ over hard coding versions in a build file. <library project="doomed" archive="dead-code" suffix=".war" destinationName="product.war" - version="LATEST" - /> + version="LATEST" /> <scheduledupdate markerfile="build/lib/marker.properties" hours="11" /> </libraries>