You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by sc...@apache.org on 2010/01/28 19:16:12 UTC

svn commit: r904196 - in /incubator/uima/site/trunk/uima-website: docs/release.html xdocs/release.xml

Author: schor
Date: Thu Jan 28 18:16:11 2010
New Revision: 904196

URL: http://svn.apache.org/viewvc?rev=904196&view=rev
Log:
no Jira - minor update to release page on what worked for 2.3.0 for maven upload

Modified:
    incubator/uima/site/trunk/uima-website/docs/release.html
    incubator/uima/site/trunk/uima-website/xdocs/release.xml

Modified: incubator/uima/site/trunk/uima-website/docs/release.html
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/release.html?rev=904196&r1=904195&r2=904196&view=diff
==============================================================================
--- incubator/uima/site/trunk/uima-website/docs/release.html (original)
+++ incubator/uima/site/trunk/uima-website/docs/release.html Thu Jan 28 18:16:11 2010
@@ -511,8 +511,10 @@
     (assuming you followed the previous release's nameing conventions for the higher-level
     directories).</p></li>
       
-		<li><p>Upload the release artifacts to the Maven Incubator repository. To start the upload the
-			following command must be executed from the uimaj project <br /><br />
+		<li><p>Upload the release artifacts to the Maven Incubator repository. To upload, first start up
+      the Pagent server (see below) so that the signon to people.apache.org can proceed.  Then go to the project 
+      where you built the release candidate, cd to uimaj, and do:
+			<br /><br />
 			<code>mvn -DsignArtifacts=true process-resources source:jar deploy</code><br /><br />
 		    Before the upload is started, make sure that the <a href="http://maven.apache.org/settings.html">Maven settings.xml</a> 
 		    file is configured properly. It must contain a section like:
@@ -541,6 +543,14 @@
       Then, when Maven executes the PuTTY commands, PAGENT will automatically provide the
       passphrase for the key. 
       </p>
+      
+      <p>This worked as of 2.3.0 release.  In the future try without 
+        including the "process-resources" goal, because
+        when done this way, you've already processed the resources as part of building the release
+        candidate.  Invoking process-resources will cause rebuilding of the jars.  
+        Also, the source:jar 
+        will probably not be needed, once the release-build process is fixed 
+        to build these automatically.</p>
 		</li>
       
  	</ul>

Modified: incubator/uima/site/trunk/uima-website/xdocs/release.xml
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/release.xml?rev=904196&r1=904195&r2=904196&view=diff
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/release.xml (original)
+++ incubator/uima/site/trunk/uima-website/xdocs/release.xml Thu Jan 28 18:16:11 2010
@@ -259,8 +259,10 @@
     (assuming you followed the previous release's nameing conventions for the higher-level
     directories).</p></li>
       
-		<li><p>Upload the release artifacts to the Maven Incubator repository. To start the upload the
-			following command must be executed from the uimaj project <br /><br/>
+		<li><p>Upload the release artifacts to the Maven Incubator repository. To upload, first start up
+      the Pagent server (see below) so that the signon to people.apache.org can proceed.  Then go to the project 
+      where you built the release candidate, cd to uimaj, and do:
+			<br /><br/>
 			<code>mvn -DsignArtifacts=true process-resources source:jar deploy</code><br/><br/>
 		    Before the upload is started, make sure that the <a href="http://maven.apache.org/settings.html">Maven settings.xml</a> 
 		    file is configured properly. It must contain a section like:
@@ -288,7 +290,15 @@
         it will prompt you for your passphrase.  
       Then, when Maven executes the PuTTY commands, PAGENT will automatically provide the
       passphrase for the key. 
-      </p>
+      </p>
+      
+      <p>This worked as of 2.3.0 release.  In the future try without 
+        including the "process-resources" goal, because
+        when done this way, you've already processed the resources as part of building the release
+        candidate.  Invoking process-resources will cause rebuilding of the jars.  
+        Also, the source:jar 
+        will probably not be needed, once the release-build process is fixed 
+        to build these automatically.</p>
 		</li>
       
  	</ul>