dion        2003/10/13 18:19:36

  Modified:    xdocs/reference/developers releasing-plugins.xml
  Log:
  Reflect current practice.
  Add example rather than link. This is handier to copy/paste.
  
  Revision  Changes    Path
  1.4       +6 -11     maven/xdocs/reference/developers/releasing-plugins.xml
  
  Index: releasing-plugins.xml
  ===================================================================
  RCS file: /home/cvs/maven/xdocs/reference/developers/releasing-plugins.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- releasing-plugins.xml     1 Sep 2003 00:31:49 -0000       1.3
  +++ releasing-plugins.xml     14 Oct 2003 01:19:36 -0000      1.4
  @@ -52,19 +52,14 @@
           </p>
         </li>
         <li>
  -        <p> Copy the new release documentation into the xdocs directory as 
  -        xdocs/releases/vX.Y and add this link to the project navigation.xml
  -        </p>
  -      </li>
  -      <li>
  -        <p> Ensure the xdocs/current directory contains a copy of xdocs/
  -        add is linked from the project navigation.xml
  -        </p>
  -      </li>
  -      <li>
           <p> Add a download link in the project navigation 
(<code>navigation.xml</code>).
  -        For an example, see <a 
href="http://maven.apache.org/reference/plugins/cactus";>cactus</a>.
  +        Example:
           </p>
  +        <source>
  +    &lt;menu name="Downloads"&gt;
  +      &lt;item name="Eclipse Plugin 1.5" 
href="http://www.ibiblio.org/maven/maven/plugins/maven-eclipse-plugin-1.5.jar"/&gt;
  +    &lt;/menu&gt;
  +        </source>
         </li>
         <li>
           <p> Create an <code>announcements</code> directory in the project and 
inside create a 
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to