Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

How Autobuild Gets Dependencies

Revision as of 16:50, 25 April 2011 by Unnamed Poltroon (Talk) (recategorized)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


  1. Nightly build runs buildLoop target of autoBuild.xml script from
  2. buildLoop iterates through each project in
    1. Checks whether the project already present at the location specified by buildDirectory property
    2. If project doesn't exist yet, try to check it out using CVS/SVN location of the project defined in
    3. Parses dependencies.xml of checked out project
    4. Iterates through each <remoteLibs> element
      • Iterates through each <library> element.
      • Checks whether library with file name specified by id attribute of <library> element already present at the location specified by the location attribute of the <remoteLibs> element
      • If library doesn't exist yet try to download and unpack it if necessary using library location specified in the
    5. Iterates through each project <higginsProjects> element and checks out all of them by repeating the above 4 steps
  3. run other targets to complete the build


See Higgins downloads

See Higgins Committers and Contributors#Processes

See Starting a Higgins Build

See How To Test Autobuild On Local Machine

Back to the top