gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@apache.org
Subject cvs commit: jakarta-gump/site/xdocs project.xml
Date Wed, 01 Jan 2003 07:24:14 GMT
dion        2002/12/31 23:24:14

  Modified:    site/xdocs project.xml
  Log:
  Update nag docs with Sam's examples from email
  
  Revision  Changes    Path
  1.13      +40 -2     jakarta-gump/site/xdocs/project.xml
  
  Index: project.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-gump/site/xdocs/project.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- project.xml	5 Jun 2002 15:12:07 -0000	1.12
  +++ project.xml	1 Jan 2003 07:24:13 -0000	1.13
  @@ -430,8 +430,8 @@
         </table>
   
         <p>A build failure is detected by matching the output of the
  -      build against Perl regular expressions, the default is
  -      <code>/BUILD FAILED/</code>.  The regular expressions are
  +      build against Perl regular expressions, the default expression
  +      is <code>/BUILD FAILED/</code>.  The regular expressions are
         specified using nested regexp elements - you can associate
         different email addresses and subjects with each expression.</p>
   
  @@ -458,6 +458,44 @@
   </nag>
   ]]></source>
   
  +       <p>
  +         Multiple <code>regexp</code> elements may be specified. The
  +         first pattern that matches will be the one used to send the
  +         nag email.
  +       </p>
  +       
  +       <p>
  +         To send email on success or failure, you could use:
  +       </p>
  +      <source><![CDATA[
  +<nag>
  +  <!-- pattern default is /BUILD FAILED/ -->
  +  <regexp from="from@example.org" 
  +          to="to@example.org" 
  +          subject="Build Failure - @name of project element@"/>
  +  <regexp pattern="/BUILD SUCCCESSFUL/"
  +          from="from@example.org" 
  +          to="to@example.org" 
  +          subject="Gump Build Success - @name of project element@"/>
  +</nag>
  +]]></source>
  +      <p>
  +        You may want to nag on deprecation if you are particularly
  +        sensitive to a given dependency. The nag for that would
  +        look like this:
  +      </p>
  +      <source><![CDATA[
  +<nag>
  +  <!-- pattern default is /BUILD FAILED/ -->
  +  <regexp from="from@example.org" 
  +          to="to@example.org" 
  +          subject="Build Failure - @name of project element@"/>
  +  <regexp pattern="/deprecat/"
  +          from="from@example.org" 
  +          to="to@example.org" 
  +          subject="Gump Build Warning - Deprecated methods used"/>
  +</nag>
  +]]></source>
       </subsection>
     </section>
   </body>
  
  
  

Mime
View raw message