poi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n...@apache.org
Subject svn commit: r1647232 - /poi/site/src/documentation/release-guide.txt
Date Mon, 22 Dec 2014 00:59:33 GMT
Author: nick
Date: Mon Dec 22 00:59:32 2014
New Revision: 1647232

URL: http://svn.apache.org/r1647232
Log:
Re-order when the maven check happens, and make the check a bit more robust

Modified:
    poi/site/src/documentation/release-guide.txt

Modified: poi/site/src/documentation/release-guide.txt
URL: http://svn.apache.org/viewvc/poi/site/src/documentation/release-guide.txt?rev=1647232&r1=1647231&r2=1647232&view=diff
==============================================================================
--- poi/site/src/documentation/release-guide.txt (original)
+++ poi/site/src/documentation/release-guide.txt Mon Dec 22 00:59:32 2014
@@ -225,35 +225,28 @@ cd build/dist
 
 When the Maven upload has completed, log into https://repository.apache.org/
 and go to the "Staging Repositories" area. Find the "orgapachepoi" entry, check
-it has the right content, then Close the repository. When that completes, Promote
-it.
+it has the right content, then Close the repository. When that completes, 
+Release it.
 
 2. Wait for the distributions to appear on your favourite mirror
 
-3. Edit the website homepage and list the new release there. If a full release,
-   remove older full releases and all beta releases. If a beta release, keep
-   the last full release, and replace any other beta releases
-
-4. Edit the website download page, and list the new release there. This should
-   reference the checksums, so take care when updating
-
-5. Build site using a recent version of Java 1.6 or 1.7 (must be after the fix
-   for TA13-169A).
-   Commit the site changes to svn, and publish live
+3. Wait for the maven artifacts to appear on Maven Central, and ensure
+   they work:
 
-6. test maven
-create a simple project and make sure the release artifacts are accessible by maven:
+Create a simple project and make sure the release artifacts are accessible 
+by maven:
 
 {code}
 $ mvn archetype:create -DgroupId=org.apache.poi.scratchpad -DartifactId=maven-test
 cd maven-test
 {code}
+
 edit pom.xml and add the release artefacts to the project dependencies: 
 
 {code:xml}
     <dependency>
       <groupId>org.apache.poi</groupId>
-      <artifactId>poi</artifactId>
+      <artifactId>poi-ooxml</artifactId>
       <version>3.11-beta1</version>
     </dependency>
     <dependency>
@@ -263,14 +256,32 @@ edit pom.xml and add the release artefac
     </dependency>
 {code}
 
+edit src/main/java/Test.java and add this:
+
+{code:java}
+import org.apache.poi.ss.usermodel.Workbook;
+import org.apache.poi.ss.usermodel.WorkbookFactory;
+
+public class Test {}
+{code}
+
 {code}
 mvn compile 
 {code}
 
-You should see [INFO] BUILD SUCCESSFUL in the end.
+You should see [INFO] BUILD SUCCESSFUL in the end, which tells you that
+the jars could be donwloaded fine.
+
+4. Edit the website homepage and list the new release there. If a full release,
+   remove older full releases and all beta releases. If a beta release, keep
+   the last full release, and replace any other beta releases
 
-Before the package is fully replicated, you may get a BUILD SUCCESSFUL, but you'll also receive
a 
-warning that the .jar can't be downloaded.  Wait until you get BUILD SUCCESSFUL and no warnings.
+5. Edit the website download page, and list the new release there. This should
+   reference the checksums, so take care when updating
+
+6. Build site using a recent version of Java 1.6 or 1.7 (must be after the fix
+   for TA13-169A).
+   Commit the site changes to svn, and publish live
 
 7. Don't forget to upload the latest version of the site and javadocs
 



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@poi.apache.org
For additional commands, e-mail: commits-help@poi.apache.org


Mime
View raw message