brett       2004/02/25 14:19:40

  Modified:    xdocs/reference/developers Tag: MAVEN-1_0-BRANCH
                        releasing-plugins.xml
  Log:
  update documentation
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.4.4.2   +12 -20    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.4.4.1
  retrieving revision 1.4.4.2
  diff -u -r1.4.4.1 -r1.4.4.2
  --- releasing-plugins.xml     23 Feb 2004 22:37:36 -0000      1.4.4.1
  +++ releasing-plugins.xml     25 Feb 2004 22:19:40 -0000      1.4.4.2
  @@ -54,30 +54,22 @@
           </p>
         </li>
         <li>
  -        <p>Modify the <code>&lt;currentVersion&gt;</code> in 
<code>project.xml</code> to remove the
  -          <code>-SNAPSHOT</code> part 
  +        <p>Run maven scm:prepare-release and enter the appropriate tag 
  +          (<code>MAVEN_[PROJECTNAME]_[MAJOR]_[MINOR]</code>) and version. This will 
update the
  +          <code>currentVersion</code>, <code>versions</code> entries, and 
<code>xdocs/changes.xml</code> file
  +          with the new version and release date. It will also commit your 
<code>project.xml</code> and
  +          <code>xdocs/changes.xml</code> files, then tag the resulting source 
tree.<br/>
  +          <b>Note:</b> This command will fail before doing any processing if there 
are modified files in your
  +          source tree other than <code>project.xml</code> and 
<code>xdocs/changes.xml</code>
           </p>
         </li>
  -      <li>
  -        <p>Modify the <code>&lt;versions&gt;/&lt;version&gt;</code> in 
<code>project.xml</code>
  -          and ensure the correct id, name and expected tag.
  -        </p>
  -      </li>
  -      <li>
  -        <p> Modify <code>changes.xml</code> to put the release date  
  -        </p>
  -      </li>
  -      <li><p>Commit your changes to CVS</p></li>
  -      <li><p>
  -        Tag the plugin project dir in CVS with 
<code>MAVEN_[PROJECTNAME]_[MAJOR]_[MINOR]</code>
  -        (for example <code>MAVEN_CACTUS_2_0</code>). 
  +      <li><p>Produce a clean build of the plugin using <code>maven 
scm:perform-release</code>.
  +        When prompted for the tag, enter the one used in the previous step. When 
prompted for the goal, enter
  +        <code>plugin:repository-deploy</code>.
         </p></li>
  -      <li><p>Produce a clean build of the plugin using <code>maven clean 
plugin</code></p></li>
         <li><p>
  -        Upload the new version to 
  -        <a 
href="http://www.ibiblio.org/maven/maven/plugins/";>http://www.ibiblio.org/maven/maven/plugins/</a>
  -        using</p><source><![CDATA[
  -maven -DgroupId=maven -Dtype=plugin -Dartifact=/path/to/file 
repository:copy-artifact]]></source>
  +        Check for the new version at
  +        <a 
href="http://www.ibiblio.org/maven/maven/plugins/";>http://www.ibiblio.org/maven/maven/plugins/</a></p>
         </li>
         <li>
           <p> Send a quick release email to the Maven user list, using the content of 
  
  
  

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

Reply via email to