Changes between Version 9 and Version 10 of Build Recipes

Timestamp:

Oct 4, 2005, 5:27:03 PM (19 years ago)

Author:

anonymous

Comment:

fix not welformed xml example

Build Recipes

@@ -24 +24 @@
   <step id="test" description="Run unit tests">
     <python:distutils command="unittest"/>
-    <python:unittest file="build/test-results.xml"/>
-    <python:trace summary="build/test-coverage.txt" 
-        coverdir="build/coverage" include="trac*" exclude="*.tests.*"/>
+    <reports>
+      <python:unittest file="build/test-results.xml"/>
+      <python:trace summary="build/test-coverage.txt" 
+          coverdir="build/coverage" include="trac*" exclude="*.tests.*"/>
     </reports>
   </step>
@@ -35 +36 @@
 == Recipe Command Binding ==
 
-Recipe commands and report generators are mapped to Python functions using [http://peak.telecommunity.com/DevCenter/PkgResources#entry-points entry points]. Bitten itself comes with a number of entry points that provide recipe commands, but third-party packages can provide additional commands by declaring their own `bitten.recipe_commands` entry points.
+Recipe commands and report generators are mapped to Python functions using [http://peak.telecommunity.com/DevCenter/PkgResources#entry-points entry points]. Bitten itself comes with a number of entry points that provide recipe commands, but third-party packages can provide additional commands by declaring their own `bitten.recipe_commands` entry points.
 
 The values of attributes on recipe command elements are passed to the function as keyword arguments. Special care must be taken with names that are either not valid Python identifiers, or that conflict with Python keywords or built-in functions. Dashes in names are replaced with underscores, and names that conflict with keywords or built-in functions get an underscore appended.