Mailing-List: contact cvs-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: 10 Oct 2003 02:15:44 -0000
Message-ID: <20031010021544.91821.qmail@minotaur.apache.org>
From: crossley@apache.org
To: cocoon-2.1-cvs@apache.org
Subject: cvs commit: cocoon-2.1 blocks.properties

crossley    2003/10/09 19:15:44

  Modified:    .        blocks.properties
  Log:
  Clarify the explanation of "deprecated blocks".
  Other minor text tweaks.
  
  Revision  Changes    Path
  1.34      +10 -10    cocoon-2.1/blocks.properties
  
  Index: blocks.properties
  ===================================================================
  RCS file: /home/cvs/cocoon-2.1/blocks.properties,v
  retrieving revision 1.33
  retrieving revision 1.34
  diff -u -r1.33 -r1.34
  --- blocks.properties	29 Sep 2003 10:18:32 -0000	1.33
  +++ blocks.properties	10 Oct 2003 02:15:43 -0000	1.34
  @@ -3,22 +3,22 @@
   #------------------------------------------------------------------------------#
   
   # Remove blocks from your cocoon distribution by uncommenting the 
  -# corresponding exclude property
  +# corresponding exclude property.
   
  -# NOTE: don't modify this file directly but make a copy named 
  +# NOTE: Don't modify this file directly but make a copy named 
   # 'local.blocks.properties' and modify that. The build system will override
   # these properties with the ones in the 'local.blocks.properties' file.
   
   # NOTE: "dependency" indicates blocks that are required by other blocks.
  -# disabling batik, for example, will prevent fop from compiling
  +# disabling batik, for example, will prevent fop from compiling.
   
   
   # Stable blocks ----------------------------------------------------------------
   
  -# stable blocks are those that can be considered ready for production and
  +# Stable blocks are those that can be considered ready for production and
   # will contain components and API that will remain stable and where
  -# developers are committed to back compatibility. In short, stuff you can
  -# depend on.
  +# developers are committed to back compatibility. In short, stuff that you
  +# can depend on.
   
   #exclude.block.authentication-fw=true
   
  @@ -54,12 +54,12 @@
   
   # Unstable blocks --------------------------------------------------------------
   
  -# unstable blocks are currently under development and do not guarantee the
  +# unstable blocks are currently under development and do not guarantee that the
   # contracts they expose (API, xml schema, properties, behavior) will remain 
   # constant in time. Developers are not committed to back-compatibility just yet.
   # This doesn't necessarily mean the blocks implementation is unstable or 
   # the code can't be trusted for production, but use with care and watch
  -# its development as thing might change over time before they are marked
  +# its development as things might change over time before they are marked
   # stable.
   
   #exclude.block.apples=true
  @@ -91,7 +91,7 @@
   
   # Deprecated blocks ------------------------------------------------------------
   
  -# Although these blocks are stable they have been deprecated in favour of other
  -# blocks.
  +# Although some of these blocks may have been stable, they are now deprecated
  +# in favour of other blocks.
   
   #exclude.block.xmlform=true