Changes between Version 5 and Version 6 of Build Recipes
- Timestamp:
- Sep 20, 2005, 7:08:34 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Build Recipes
v5 v6 14 14 #!xml 15 15 <build description="My project" 16 xmlns:python="bitten:bitten. recipe.pythontools">16 xmlns:python="bitten:bitten.build.pythontools"> 17 17 18 18 <step id="build" description="Compile to byte code"> 19 <p thon:distutils command="build"/>19 <python:distutils command="build"/> 20 20 </step> 21 21 22 22 <step id="test" description="Run unit tests"> 23 <p thon:distutils command="unittest"/>23 <python:distutils command="unittest"/> 24 24 <reports> 25 25 <python:unittest file="build/test-results.xml"/> … … 36 36 As 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. 37 37 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.38 For 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. 39 39 40 40 So, the XML snippet: