Author: aheritier
Date: Tue Jun 19 08:16:45 2007
New Revision: 548760

URL: http://svn.apache.org/viewvc?view=rev&rev=548760
Log:
some updates about sources

Modified:
    maven/maven-1/core/trunk/xdocs/developers/making-releases.xml

Modified: maven/maven-1/core/trunk/xdocs/developers/making-releases.xml
URL: 
http://svn.apache.org/viewvc/maven/maven-1/core/trunk/xdocs/developers/making-releases.xml?view=diff&rev=548760&r1=548759&r2=548760
==============================================================================
--- maven/maven-1/core/trunk/xdocs/developers/making-releases.xml (original)
+++ maven/maven-1/core/trunk/xdocs/developers/making-releases.xml Tue Jun 19 
08:16:45 2007
@@ -106,7 +106,7 @@
           <p>Run <code>maven scm:prepare-release</code> and enter the 
appropriate tag (<code>maven-[major].[minor].[bugfix]</code>) and version.</p>
         </li>
         <li>
-          <p>Produce a clean build using <code>maven 
-Dmaven.repo.list=apache.releases -Dmaven.site.deploy.live=true 
scm:perform-release</code>. When prompted for the tag, enter the one used in 
the previous step. When prompted for the goal, enter 
<code>maven:release</code>. Do this on Windows so that the .exe file is 
generated (you have to install NSIS, and to setup the NSIS plugin to find the 
exe). You can find the binaries in 
<code>target/checkout/target/distribution</code></p>
+          <p>Produce a clean build using <code>maven 
-Dmaven.repo.list=apache.releases scm:perform-release</code>. When prompted for 
the tag, enter the one used in the previous step. When prompted for the goal, 
enter <code>maven:release</code>. Do this on Windows so that the .exe file is 
generated (you have to install NSIS, and to setup the NSIS plugin to find the 
exe). You can find the binaries in 
<code>target/checkout/target/distribution</code></p>
         </li>
         <li>
           <p>Sign and create checksums for the binaries :</p>
@@ -126,16 +126,16 @@
 ]]></source>
         </li>
         <li>
-          <p>Manually upload the distributions on 
<code>people.apache.org</code> to the distribution location (under 
<code>/www/www.apache.org/dist/maven/binaries/</code>).</p>
+          <p>Manually upload the distributions on 
<code>people.apache.org</code> to the distributions locations (under 
<code>/www/www.apache.org/dist/maven/binaries/</code> and 
<code>/www/www.apache.org/dist/maven/source/</code>).</p>
         </li>
         <li>
-          <p>Check for the new version at <a 
href="http://www.apache.org/dist/maven/binaries/";>http://www.apache.org/dist/maven/binaries/</a>.</p>
+          <p>Check for the new version at <a 
href="http://www.apache.org/dist/maven/binaries/";>http://www.apache.org/dist/maven/binaries/</a>
 and <a 
href="http://www.apache.org/dist/maven/source/";>http://www.apache.org/dist/maven/source/</a>.</p>
         </li>
         <li>
           <p>Go to the <a 
href="http://jira.codehaus.org/secure/project/ManageVersions.jspa?pid=10030";>JIRA
 administration page</a> for the Maven project (Note that you need to be a JIRA 
administrator for this project) and <strong>release</strong> the version. Also 
make sure to <strong>add</strong> a new version for the following development 
version. This is required so that developers can assign a "fix for" version to 
issues.</p>
         </li>
         <li>
-          <p>Run <code>scm:perform-release</code> with the 
<code>site:deploy</code> goal, and mail out release notes</p>
+          <p>Run <code>scm:perform-release 
-Dmaven.site.deploy.live=true</code> with the <code>site:deploy</code> goal, 
and mail out release notes</p>
         </li>
       </ul>
     </section>


Reply via email to