Edgewall Software

Changes between Version 5 and Version 6 of Build Recipes


Ignore:
Timestamp:
Sep 20, 2005, 7:08:34 PM (19 years ago)
Author:
cmlenz
Comment:

Corrections for #50

Legend:

Unmodified
Added
Removed
Modified
  • Build Recipes

    v5 v6  
    1414#!xml
    1515<build description="My project"
    16     xmlns:python="bitten:bitten.recipe.pythontools">
     16    xmlns:python="bitten:bitten.build.pythontools">
    1717
    1818  <step id="build" description="Compile to byte code">
    19     <pthon:distutils command="build"/>
     19    <python:distutils command="build"/>
    2020  </step>
    2121
    2222  <step id="test" description="Run unit tests">
    23     <pthon:distutils command="unittest"/>
     23    <python:distutils command="unittest"/>
    2424    <reports>
    2525      <python:unittest file="build/test-results.xml"/>
     
    3636As noted above, recipe commands and report generators are mapped to Python modules using XML namespaces. The URI of recipe namespace that uses the ''bitten'' scheme is mapped to the corresponding module. Commands and report generators are then mapped to functions inside that module.
    3737
    38 For example, the command `<python:distutils>` (where the namespace prefix `bitten` resolves to `bitten:bitten.build.pythontools`) is mapped to the function `distutils` in the `bitten.build.pythontools` module. The function is invoked with any provided attributes passed as keyword arguments.
     38For example, the command `<python:distutils>` (where the namespace prefix `python` resolves to `bitten:bitten.build.pythontools`) is mapped to the function `distutils` in the `bitten.build.pythontools` module. The function is invoked with any provided attributes passed as keyword arguments.
    3939
    4040So, the XML snippet: