commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nia...@apache.org
Subject svn commit: r922462 - /commons/proper/commons-site/src/site/xdoc/releases/release.xml
Date Sat, 13 Mar 2010 00:52:56 GMT
Author: niallp
Date: Sat Mar 13 00:52:55 2010
New Revision: 922462

URL: http://svn.apache.org/viewvc?rev=922462&view=rev
Log:
Tweak instructions for m2

Modified:
    commons/proper/commons-site/src/site/xdoc/releases/release.xml

Modified: commons/proper/commons-site/src/site/xdoc/releases/release.xml
URL: http://svn.apache.org/viewvc/commons/proper/commons-site/src/site/xdoc/releases/release.xml?rev=922462&r1=922461&r2=922462&view=diff
==============================================================================
--- commons/proper/commons-site/src/site/xdoc/releases/release.xml (original)
+++ commons/proper/commons-site/src/site/xdoc/releases/release.xml Sat Mar 13 00:52:55 2010
@@ -50,7 +50,7 @@
     In particular, it is assumed:
     <ul>
       <li>
-        The build version for the component has been updated to the release number in project.xml
+        The build version for the component has been updated to the release number in pom.xml
       </li>
       <li>
         The build version for the component has been updated to the release number in build.xml
if
@@ -354,52 +354,24 @@ gpg: Good signature from "Robert Burrell
     </p>
   </subsection>
 
-  <subsection name='8 Deploy jar, project.xml and license.html to Java-Repository'>
+  <subsection name='8 Deploy Maven Artifacts to Java-Repository'>
     <p>
     The ASF Java Respository is the home for distributions in jar format.
-    Your jar file(s) should be placed in 
-    <code>/www/people.apache.org/repo/m1-ibiblio-rsync-repository/commons-foo/jars</code>
on
-    people.apache.org. The jars placed here will be rsynched (after some delay)
-    to the public distribution repository on www.apache.org, as well as to the
-    ibiblio repository. If available, your project.xml should be placed in 
-    <code>/www/people.apache.org/repo/m1-ibiblio-rsync-repository/commons-foo/poms</code>
-    as the file <code>commons-foo-1.2.pom</code>. 
-    Ensure the version number matches the one inside the <code>project.xml</code>.
+    Your maven artifacts (jar and  pom, files) should be placed in 
+    <code>/www/people.apache.org/repo/m2-ibiblio-rsync-repository/commons-foo/commons-foo/1.2/</code>
+    on people.apache.org.
+    </p>
+    <p>
+    The updated <code>maven-metadata.xml</code> file should be placed in 
+    <code>/www/people.apache.org/repo/m2-ibiblio-rsync-repository/commons-foo/commons-foo/</code>
+    on people.apache.org.
     </p>
     <p><strong>N.B.</strong> Remember to sign files placed in the ASF Java
        Respository.
     </p>
     <p>
-    The current html version of the Apache Software License needs to be in 
-    /www/people.apache.org/repo/m1-ibiblio-rsync-repository/commons-foo/licenses as the file
-    license.html. If this file does not exist or reflects an out-of-date version,
-    copy a current version from another component directory. There should also be
-    a symlink named commons-foo.license in this directory. If this link does not
-    exist, create it using
-    <pre>
-      ln -s license.html commons-foo.license 
-    </pre>
-    </p>
-    <p>
-    Maven users can deploy release jars automatically using maven's jar plugin.
-    See the 
-<a href="http://svn.apache.org/repos/asf/commons/proper/commons-build/trunk/samples/project.properties.sample">
-    project.properties.sample</a> file in the commons-build directory for
-    an example showing how to configure the necessary properties to support jar
-    deployment using scp. A how-to showing how to get an apache ssh key set up
-    can be found  
-    <a href="http://www.apache.org/dev/user-ssh.html">
-    here.</a>  Given this setup, 
-    <pre>
-      maven -Dmaven.repo.list=apache.releases -Duser.name=your-apache-id jar:deploy
-    </pre>
-    will deploy the jar to the Apache Maven repository (with your user name
-    as the value of the Built-By attribute in the manifest). Note that the
-    maven jar plugin does not (yet) create or publish signatures, so if you use
-    maven to deploy the jar, you need to manually sign it and copy the signature
-    file separately to /www/people.apache.org/repo/m1-ibiblio-rsync-repository/commons-foo/jars.
-    Make sure that the signature file has correct permissions and group
-    ownership (matching the jar) after you copy it. 
+    The files placed here will be rsynched (after some delay) to the public distribution
+    repository on <a href="http://repo1.maven.org/maven2/">http://repo1.maven.org/maven2/</a>.
     </p>
   </subsection>
 
@@ -530,7 +502,7 @@ gpg: Good signature from "Robert Burrell
     </li>
     <li>
     <strong>Update currentVersion</strong>
-    Update currentVersion found in <code>project.xml</code> in the trunk. This
should be
+    Update currentVersion found in <code>pom.xml</code> in the trunk. This should
be
     updated to a <code>SNAPSHOT</code> release, eg change "1.2" to "1.3-SNAPSHOT"
     </li>
     </ul>



Mime
View raw message