You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openjpa.apache.org by bu...@apache.org on 2012/12/09 14:13:50 UTC
svn commit: r841236 [30/35] - in /websites/staging/openjpa/trunk/content: ./
artifacts/ css/ images/ images/datacache-plugin/
Added: websites/staging/openjpa/trunk/content/releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps).html
==============================================================================
--- websites/staging/openjpa/trunk/content/releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps).html (added)
+++ websites/staging/openjpa/trunk/content/releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps).html Sun Dec 9 13:13:35 2012
@@ -0,0 +1,706 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+<html lang="en">
+ <head>
+ <META http-equiv="Content-Type" content="text/html;charset=UTF-8" />
+ <link href="http://openjpa.apache.org/styles/site.css" rel="stylesheet" type="text/css"/>
+ <!-- <link href="http://openjpa.apache.org/styles/type-settings.css" rel="stylesheet" type="text/css"/> -->
+ <link href="./css/type-settings.css" rel="stylesheet" type="text/css"/>
+ <LINK rel="schema.DC" href="http://purl.org/DC/elements/1.0/">
+ <META name="Description" content="Apache OpenJPA -- Releasing OpenJPA 1.0.x or 1.1.x (Old SCP Steps)
" />
+ <META name="Keywords" content="Apache OpenJPA, JPA, JPA 1.0, JSR-220, JPA2, JPA 2.0, JSR-317, " />
+ <META name="Owner" content="dev@openjpa.apache.org" />
+ <META name="Robots" content="index, follow" />
+ <META name="Security" content="Public" />
+ <META name="Source" content="wiki template" />
+ <META name="DC.Date" scheme="iso8601" content="2010-08-11" />
+ <META name="DC.Language" scheme="rfc1766" content="en" />
+ <META name="DC.Rights" content="Copyright © 2006,2010 The Apache Software Foundation" />
+ <META http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))'/>
+
+ <title>
+ Apache OpenJPA --
+ </title>
+ </head>
+ <body>
+ <div class="white_box">
+ <div class="header">
+ <div class="header_l">
+ <div class="header_r">
+ </div>
+ </div>
+ </div>
+ <div class="content">
+ <div class="content_l">
+ <div class="content_r">
+ <div>
+ <!-- Banner -->
+ <TABLE valign="top" border="0" cellspacing="0" cellpadding="5" width="100%" background="images/header-bg3.png">
+ <TR>
+ <TD valing="top" align="left">
+ <A href="http://openjpa.apache.org/"><IMG src="images/openjpa-logo.png" border="0" alt="OpenJPA Logo"></A>
+ </TD>
+ <TD width="100%">
+
+ </TD>
+ <TD valing="top" align="right">
+ <A href="http://www.apache.org/"><IMG src="images/asf_logo_wide2.png" border="0" alt="ASF Logo"></A>
+ </TD>
+ </TR>
+ </TABLE>
+
+ <!-- Navigation Bar -->
+ <div class="bottom_red_bar">
+ <div id="site-breadcrumbs">
+ <!-- Breadcrumbs --
+ <a href="/">Home</a> » <a href="/releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps).html">Releasing OpenJPA 1.0.x or 1.1.x (Old SCP Steps)
</a>
+ -- Breadcrumbs -->
+ </div>
+ </div>
+
+ <!-- Content -->
+ <table border="0">
+ <tbody>
+ <tr>
+ <td valign="top">
+ <div class="navigation">
+ <div class="navigation_top">
+ <div class="navigation_bottom">
+ <!-- NavigationBar -->
+ <h3><a name="SideNav-Overview"></a><a href="overview.html" title="Overview">Overview</a></h3>
+
+ <ul class="alternate" type="square">
+ <li><a href="quick-start.html" title="Quick Start">Quick Start</a></li>
+ <li><a href="documentation.html" title="Documentation">Documentation</a></li>
+ <li><a href="downloads.html" title="Downloads">Downloads</a></li>
+ <li><a href="site-index.html" title="Site Index">Site Index</a></li>
+ <li><a href="license.html" title="License">License</a></li>
+ <li><a href="privacy-policy.html" title="Privacy Policy">Privacy Policy</a></li>
+ </ul>
+
+ <h3><a name="SideNav-Community"></a><a href="community.html" title="Community">Community</a></h3>
+
+ <ul class="alternate" type="square">
+ <li><a href="index.html#Index-eventsandnews" title="Events and News">Events and News</a></li>
+ <li><a href="found-a-bug.html" title="Found a Bug">Found a Bug</a>?</li>
+ <li><a href="get-involved.html" title="Get Involved">Get Involved</a></li>
+ <li><a href="mailing-lists.html" title="Mailing Lists">Mailing Lists</a></li>
+ <li><a href="committers.html" title="Committers">Committers</a></li>
+ <li><a href="integration.html" title="Integration">Integration</a></li>
+ <li><a href="powered-by.html" title="Powered By">Powered By</a></li>
+ <li><a href="thanks.html" title="Thanks">Thanks</a></li>
+ </ul>
+
+
+ <h3><a name="SideNav-Development"></a><a href="development.html" title="Development">Development</a></h3>
+
+ <ul class="alternate" type="square">
+ <li><a href="http://issues.apache.org/jira/browse/OPENJPA" class="external-link" rel="nofollow">Issue Tracker</a></li>
+ <li><a href="source-code.html" title="Source Code">Source Code</a></li>
+ <li><a href="testing.html" title="Testing">Testing</a></li>
+ <li><a href="tools.html" title="Tools">Tools</a></li>
+ <li><a href="samples.html" title="Samples">Samples</a></li>
+ <li><a href="release-management.html" title="Release Management">Release Management</a></li>
+ </ul>
+
+ <h3>Search</h3>
+
+ <div style="padding: 5px 5px 0px 25px;">
+ <form action="http://www.google.com/search" method="get" style="font-size: 10px;">
+ <input name="ie" type="hidden" value="UTF-8">
+ <input name="oe" type="hidden" value="UTF-8">
+ <input maxlength="255" name="q" size="9" type="text" value=""><br><br>
+ <input name="btnG" type="submit" value="Google">
+ <input name="domains" type="hidden" value="openjpa.apache.org">
+ <input name="sitesearch" type="hidden" value="openjpa.apache.org">
+ </form>
+ </div>
+ </div>
+ </div>
+ </div>
+ </td>
+ <td valign="top" width="100%" style="overflow:hidden;">
+ <div class="wiki-content">
+ <p><a name="ReleasingOpenJPA1.0.xor1.1.x(OldSCPSteps)-MakinganOpenJPA1.0.xor1.1.xRelease"></a></p>
+<h1 id="making-an-openjpa-10x-or-11x-release">Making an OpenJPA 1.0.x or 1.1.x Release</h1>
+<p>These instructions guide the release manager through the steps of making an
+official OpenJPA release.</p>
+<p><a name="ReleasingOpenJPA1.0.xor1.1.x(OldSCPSteps)-Prerequisites"></a></p>
+<h2 id="prerequisites">Prerequisites</h2>
+<ol>
+<li>You should read the <a href="openjpa-release-policy.html">OpenJPA Release Policy</a>
+ to decide on the name of the new release, based on the content.</li>
+<li>You should read the Apache <a href="http://www.apache.org/dev/release.html">Release FAQ</a></li>
+<li>You must have shell access to people.apache.org</li>
+<li>You must have the following utilities installed on your local machine and
+available in your path:<ul>
+<li><a href="http://java.sun.com/">JDK 1.4 / 1.5</a></li>
+<li><a href="http://www.openssh.com/">ssh</a></li>
+<li><a href="http://maven.apache.org/">Maven 2</a></li>
+<li><a href="http://www.gnupg.org/">gnupg</a></li>
+</ul>
+</li>
+<li>For Windows users, install <a href="http://cygwin.com/">Cygwin</a>
+ in addition to the above utilities<ul>
+<li>Make sure the Net/openssh and Utils/gnupg packages are installed that
+come with Cygwin installation. </li>
+<li>Optional: <a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/">Putty</a></li>
+</ul>
+</li>
+</ol>
+<p><a name="ReleasingOpenJPA1.0.xor1.1.x(OldSCPSteps)-Tasksthatneedtobeperformedforeachrelease"></a></p>
+<h2 id="tasks-that-need-to-be-performed-for-each-release">Tasks that need to be performed for each release</h2>
+<p>{info}In the examples below, it is assumed that the release name will be
+<strong>1.0.1</strong>, and that the current checked-in version name is <strong>1.0.1-SNAPSHOT</strong>
+and stored in the branch named <em>1.0.x</em>.{info}</p>
+<p>{code:none}
+svn copy -m "OpenJPA Release 1.0.1 branch" \
+ https://svn.apache.org/repos/asf/openjpa/branches/1.0.x \
+ https://svn.apache.org/repos/asf/openjpa/branches/1.0.1</p>
+<div class="codehilite"><pre><span class="o">||</span> <span class="n">Monday</span><span class="p">,</span> <span class="mi">12</span><span class="p">:</span><span class="mo">02</span> <span class="o">|</span> <span class="n">Check</span> <span class="n">out</span> <span class="n">a</span> <span class="n">clean</span> <span class="n">branch</span> <span class="n">from</span> <span class="n">which</span> <span class="n">to</span> <span class="n">build</span> <span class="n">the</span>
+</pre></div>
+
+
+<p>release: \
+ {code:none}
+ svn checkout https://svn.apache.org/repos/asf/openjpa/branches/1.0.1
+ cd 1.0.1</p>
+<p>{note}Make sure there is no space characters in the path to the build root subdirectory, i.e. "c:\OpenJPA 1.0.1 Release\build". See "<a href="#space-character-in-build-root-path.html">#Space Character in Build Root Path</a>
+"{note} ||</p>
+<p>{code:none}
+perl -pi -e
+"s;<version>1.0.1-SNAPSHOT</version>;<version>1.0.1</version>;g" \
+ pom.xml <em>/pom.xml </em>/*/pom.xml</p>
+<div class="codehilite"><pre><span class="n">Update</span> <span class="n">the</span> <span class="p">{{</span><span class="sr"><scm.dir></span><span class="p">}}</span> <span class="n">property</span> <span class="n">in</span> <span class="n">the</span> <span class="n">top</span> <span class="n">level</span> <span class="n">pom</span><span class="o">.</span><span class="n">xml</span> <span class="n">to</span> <span class="n">the</span> <span class="mf">1.0.1</span>
+</pre></div>
+
+
+<p>release. \
+ Update the {{<developer>}} element in the top level pom.xml if new
+committers are added or removed. This applies to the 1.0.x branch only. ||
+ || Monday, 12:10 | Verify that LICENSE.txt contains up to date licenses for
+any dependencies which are included in our distribution.\ Any jars or
+source code which is included with the OpenJPA distribution that is not
+covered by the Apache license must be noted in LICENSE.txt. Two examples of
+this are the persistence and orm dtds (licensed under the CDDL) and Serp.
+If any new non Apache dependencies have been introduced they will have to
+be covered here as well. If any discrepancies are found update LICENSE.txt
+and commit the changes. \ ||
+ || Monday, 12:15 | Update BUILDING.txt, CHANGES.txt and RELEASE-NOTES.html
+\
+ * BUILDING.txt should be included in the source tarball and contains
+instructions on how to build OpenJPA. Prior to shipping a release we should
+ensure that those instructions are accurate.
+ * CHANGES.txt contains a text representation of all the changes which have
+been made since the preceding release. Most of the contents of this file
+can be generated through JIRA's release notes mechanism [here|http://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310351]
+ * RELEASE-NOTES.html contains general information on the OpenJPA project as
+well as an html version of the changes since the preceding version. The
+html change log may also be generated via JIRA.\
+ ||
+ || Monday, 12:20 | Commit the POM changes \
+ {code:none}
+ svn commit -m "Updated to version 1.0.1 for the release"</p>
+<p>{code:none}
+mvn clean install -Dtest=false</p>
+<div class="codehilite"><pre><span class="o">||</span> <span class="n">Monday</span><span class="p">,</span> <span class="mi">12</span><span class="p">:</span><span class="mi">23</span> <span class="o">|</span> <span class="n">Now</span> <span class="n">build</span> <span class="n">the</span> <span class="n">release</span> <span class="n">locally</span><span class="p">,</span> <span class="n">which</span> <span class="n">will</span> <span class="n">build</span> <span class="ow">and</span>
+</pre></div>
+
+
+<p>test, run the Apache [Release Audit Tool|http://mojo.codehaus.org/rat-maven-plugin/]
+ to verify license headers, generate the javadoc and docbook PDF and HTML,
+run through the JPA TCK, build the source and binariy assemblies in
+<em>target/site/downloads/</em>, and sign the release files. \
+ {code:none}
+ export MAVEN_OPTS=-Xmx1000m
+ mvn --batch-mode deploy site \</p>
+<p>-Ptck-profile,examples-profile,license-verify-profile,javadoc-profile,docbook-profile,sign-release
+\
+ -Djava14.jar=${JAVA_HOME}/../../1.4/Classes/classes.jar \
+ -Dtck.zip=${HOME}/.m2/privaterepos/jpa-1_0b-tck.zip</p>
+<p>{note} The <em>examples-profile</em> has problem running automatically in this
+maven build task. You will need to run the examples manually. Run the maven
+command without the <em>examples-profile</em>, then perform the following steps
+to run the example:</p>
+<div class="codehilite"><pre><span class="nb">mkdir</span> <span class="n">openjpa</span><span class="o">-</span><span class="n">integration</span><span class="o">\</span><span class="n">examples</span><span class="o">\</span><span class="n">target</span><span class="o">\</span><span class="n">examples</span>
+<span class="n">unzip</span> <span class="n">target</span><span class="o">\</span><span class="n">site</span><span class="o">\</span><span class="n">downloads</span><span class="o">\</span><span class="n">apache</span><span class="o">-</span><span class="n">openjpa</span><span class="o">-</span><span class="mf">1.0.1</span><span class="o">-</span><span class="n">binary</span><span class="o">.</span><span class="n">zip</span> <span class="o">-</span><span class="n">d</span>
+</pre></div>
+
+
+<p>openjpa-integration\examples\target\examples
+ cd
+openjpa-integration\examples\target\examples\apache-openjpa-1.0.1\examples\hellojpa
+ ant
+ cd ..\relations
+ ant
+ cd ..\reversemapping
+ ant</p>
+<p>{note} ||</p>
+<p>{code:none}
+gpg --multifile --verify target/site/downloads/*.asc</p>
+<div class="codehilite"><pre><span class="o">||</span> <span class="n">Monday</span><span class="p">,</span> <span class="mi">13</span><span class="p">:</span><span class="mo">01</span> <span class="o">|</span> <span class="n">Upload</span> <span class="n">the</span> <span class="n">release</span> <span class="n">candidate</span> <span class="n">to</span> <span class="p">[</span><span class="n">http:</span><span class="sr">//o</span><span class="n">penjpa</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/builds/</span><span class="mf">1.0.1</span><span class="sr">/downloads/</span><span class="p">]</span>
+</pre></div>
+
+
+<dl>
+<dd>\
+{code:none}
+mvn site:deploy</dd>
+</dl>
+<p>Bear in mind that uploads to
+<em>people.apache.org/www/openjpa.apache.org/builds/</em> are not visible at <a href="http://openjpa.apache.org/builds">http://openjpa.apache.org/builds</a>
+ until after the hourly synchronization has taken place, as described at [http://www.apache.org/dev/project-site.html]
+.
+{warning}||
+<table>
+<tr><th> Monday, 15:00 </td><td> Start a vote for the release on the <a href="mailto:dev@openjpa.apache.org.html">mailto:dev@openjpa.apache.org</a>
+ mailing list. Votes made by committers and members of the OpenJPA project
+are considered binding for this vote. For an example of the mail, see [this archived 1.0.0 vote</td><td>http://www.nabble.com/-VOTE--Approve-OpenJPA-1.0.0-release-%284th-attempt%29-p12305349.html]
+ </th></tr>
+<tr><th> Tuesday, Wednesday </td><td> While waiting for the vote to complete, perform
+whatever manual review and testing on the release you deem appropriate. </th></tr></p>
+<p>{code:none}
+ssh people.apache.org
+cp -r /www/openjpa.apache.org/builds/1.0.1/downloads/*
+/www/www.apache.org/dist/openjpa/1.0.1
+chgrp -R openjpa /www/www.apache.org/dist/openjpa/1.0.1
+chmod -R g+w /www/www.apache.org/dist/openjpa/1.0.1</p>
+<div class="codehilite"><pre><span class="n">The</span> <span class="n">OpenJPA</span> <span class="n">binary</span> <span class="n">release</span> <span class="n">will</span> <span class="n">be</span> <span class="n">available</span> <span class="n">via</span> <span class="n">the</span> <span class="nb">link</span> <span class="p">[</span><span class="n">http:</span><span class="sr">//</span><span class="n">www</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/dyn/c</span><span class="n">loser</span><span class="o">.</span><span class="n">cgi</span><span class="sr">/openjpa/</span><span class="mf">1.0.1</span><span class="o">/</span><span class="n">apache</span><span class="o">-</span><span class="n">openjpa</span><span class="o">-</span><span class="mf">1.0.1</span><span class="o">-</span><span class="n">binary</span><span class="o">.</span><span class="n">zip</span><span class="p">]</span>
+</pre></div>
+
+
+<p>after 24 hours, as per the [Apache mirroring information|http://apache.org/dev/mirrors.html]
+.
+ {warning}||
+ || Thursday, 15:15 | Now that the release is locked down, convert the
+writeable 1.0.1 branch to a (du jure) read-only tag: \
+ {code:none}
+ svn mv -m "OpenJPA Release 1.0.1 tag" \
+ https://svn.apache.org/repos/asf/openjpa/branches/1.0.1 \
+ https://svn.apache.org/repos/asf/openjpa/tags/1.0.1</p>
+<p>{code:none}
+svn checkout https://svn.apache.org/repos/asf/openjpa/branches/1.0.x
+cd 1.0.x
+perl -pi -e
+"s;<version>1.0.1-SNAPSHOT</version>;<version>1.0.2-SNAPSHOT</version>;g" \
+ pom.xml <em>/pom.xml </em>/*/pom.xml
+svn commit -m "Updating version in branch to 1.0.2-SNAPSHOT"</p>
+<div class="codehilite"><pre><span class="o">||</span> <span class="n">Thursday</span><span class="p">,</span> <span class="mi">15</span><span class="p">:</span><span class="mi">20</span> <span class="o">|</span> <span class="n">Update</span> <span class="n">the</span> <span class="p">[</span><span class="n">http:</span><span class="sr">//c</span><span class="n">wiki</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/openjpa/</span><span class="n">downloads</span><span class="o">.</span><span class="n">html</span><span class="p">]</span>
+</pre></div>
+
+
+<p>page with links to the download mirrors, using the existing entries as
+templates. {note}All artifacts (<em>apache-openjpa-1.0.1-binary.zip</em> and
+<em>apache-openjpa-1.0.1-source.zip</em>) <em>must</em> link to the mirrors, but
+signatures (<em>apache-openjpa-1.0.1-binary.zip.asc</em> and
+<em>apache-openjpa-1.0.1-source.zip.asc</em>) <em>must not</em> link to mirrors.{note}||
+ || Thursday, 15:30 | The documentation on the server-side must manually be
+extracted on <em>people.apache.org</em>, and the links at [http://openjpa.apache.org/documentation.html]
+ need to be updated with the new versions and the "latest" documentation
+symbolic links need to be updated: \
+ {code:none}
+ cd /www/openjpa.apache.org/builds/1.0.1/
+ unzip downloads/apache-openjpa-1.0.1-binary.zip
+ rm /www/openjpa.apache.org/docs/latest
+ ln -fvs ../builds/1.0.1/apache-openjpa-1.0.1/docs/
+/www/openjpa.apache.org/docs/latest</p>
+<table>
+<tr></tr>
+
+{code:none}
+svn co
+http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-stage-plugin/ \
+ /tmp/maven-stage-plugin
+mvn -f /tmp/maven-stage-plugin/pom.xml clean install
+for i in $(find openjpa-* -name m2-repository | egrep -v
+"openjpa-project|openjpa-integration|openjpa-examples"); do
+ cd $i
+ mvn stage:copy -Dsource=file://. \
+
+-Dtarget=scp://people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+\
+ -Dversion=1.0.1
+ cd -
+done
+
+ This process requires Maven 2.0.5. It is currently quite delicate and
+error-prone. Once the *maven-stage-plugin* is released, it should be
+possible to make it more automated.
+ {warning}
+ {info}
+ Window/Cygwin user: See [#Merging local repository to remote repository in Cygwin/Windows]
+ {info}
+ {info}
+ Linux users: You may need to change the '-Dsource=' option to read
+'-Dsource=file:{}'. The file://{} syntax may result in errors creating the
+wagon file with errors like: "Repository path
+/openjpa-jdbc-5/target/site/m2-repository does not exist, and cannot be
+created."
+ {info}
+ || Thursday, 16:00 | Update the [JIRA versions | https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12310351]
+ page to mark the version as "released", and set the date to the date that
+the release was approved. You may also need to make a new release entry for
+the subsequent release.||
+ || Friday, 16:00 | After the mirrors have had time to update (24 hours to
+be on the safe side), make a [news announcement|http://cwiki.apache.org/confluence/pages/createblogpost.action?spaceKey=openjpa]
+ on the OpenJPA wiki. {note}Once the news item is made, it won't show up on
+the [front page|http://cwiki.apache.org/openjpa/]
+ unless you make some minor edit to the containing page (e.g., adding a
+newline somewhere).{note} ||
+ || Friday, 16:05 | Make an announcement about the release on the [mailto:users@openjpa.apache.org]
+ list (and, for major releases, on the [mailto:announce@apache.org]
+ list as per [the Apache Announcement Mailing Lists page|http://www.apache.org/foundation/mailinglists.html#foundation-announce]
+). The announcement might look something like [this|http://www.nabble.com/-ANNOUNCE--Apache-OpenJPA-1.0.0-released-p12397604.html]
+. ||
+ || Friday, 16:10 | Make an announcement for the [freshmeat.net OpenJPA project|http://freshmeat.net/projects/openjpa/]
+ (optional) ||
+ || Friday, 17:00 | Have a beer and enjoy your weekend while the world's
+grateful programmers revel in yet another high-quality release of Apache
+OpenJPA! ||
+
+ h2. One time setup
+
+ These setup steps only need to be performed on a particular machine once.
+ {info}Developers using Linux workstations can skip over the references to
+PuTTY and Cygwin
+ {info}
+
+ h3. Create and install a SSH key
+
+ || 1 | Install PuTTY ||
+ || 2a | Use ssh-keygen to create a SSH key.
+ {info} See [Authenticating By Public Key (OpenSSH)|http://www.networknewz.com/networknewz-10-20030707AuthenticatingbyPublicKeyOpenSSH.html]
+ for a good description on why and how to perform this task.
+ {info} ||
+ || 2b | In Windows platform, use PuttyGen to create a SSH key (see Putty
+help for details).
+ {info}
+ * Use "*SSH-2 DSA*" key type and *1024*-bit key size.
+ * Copy the content of the "Public key for pasting...." and save it to a
+file named {{authorized_keys}} for later use.
+ * The private key saved by PuTTYGen can only be used in Putty
+configuration.
+ {info} ||
+ || 3 | {{pscp}} your SSH public key {{authorized_keys}} saved in last step
+to {{\~/authorized_keys}} ||
+ || 4 | Use PuTTY to login to people.apache.org ||
+ || 5 | Create a {{\~\.ssh}} folder and change its file mode to 700.
+ || 6 | Move or append {{\~/authorized_keys}} to {{\~/.ssh/authorized_keys}}
+and change its file mode to 600.
+ {info}
+ * Each public key in the {{authorized_keys}} spans only one line.
+ ** For example: "{{ssh-dss AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA==
+dsa-key-20071107}}"
+ * '#' in the first column is a comment line.
+ {info} ||
+ || 7 | Configure putty to use your private key and save the session
+ {info}
+ Specify your private key in the "Connection -> SSH -> Auth" category in
+Putty configuration.
+ {info}
+ ||
+
+ h3. Create a PGP key
+
+ || 1 | Install cgywin, including *Utils/gnupg* and *Net/openssh* packages, or install gpg from {{[http://www.gnupg.org/(en)/download/index.html]
+}} ||
+ || 2 | Generate a key-pair with {{$ gpg \--gen-key}} using default key kind
+("DSA and Elgamal") and ELG-E keys size (2048).
+ {info}
+ * The generated keys are stored in $HOME/.gnupg or %HOME%\Application
+Data\gnupg subdirectory.
+ * Save the content in this subdirectory to a safe media. This contains your
+private key used to sign all the OpenJPA release materials.
+ {info} ||
+ || 3 | Backup your cygwin home directory to another media ||
+ || 4 | Add your public key to {{[https://svn.apache.org/repos/asf/openjpa/site/docs/KEYS]
+}} and {{/www/www.apache.org/dist/openjpa/KEYS}}. See the commands describe
+at the beginning of this KEYS file to perform this task. The gpg key-pair
+is used to sign the published artifacts for the OpenJPA releases. ||
+ || 5 | Following the instructions in [http://people.apache.org/~henkp/trust/]
+ and ask someone in the OpenJPA project to sign your public key. ||
+ || 6 | Submit your public key to a key server. E.g. [http://pgp.surfnet.nl:11371/]
+ or [http://pgp.mit.edu/]
+||
+
+ h3. Update Maven settings for our servers
+
+ || 1 | Create a settings.xml under .m2 (in your Document and Settings
+folder in Windows) ||
+ | | {code:xml|title=settings.xml|borderStyle=solid}
+ <settings xmlns="http://maven.apache.org/POM/4.0.0"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
+http://maven.apache.org/xsd/settings-1.0.0.xsd">
+ <servers>
+ <server>
+ <id>people.apache.org</id>
+ <username>$USERNAME</username>
+ <privateKey>$PATH_TO_PRIVATE_KEY</privateKey>
+ <directoryPermissions>775</directoryPermissions>
+ <filePermissions>644</filePermissions>
+ </server>
+ </servers>
+ </settings>
+
+{info}
+*$PATH_TO_PRIVATE_KEY* is the path to the private key generated for ssh.
+E.g. /home/yourLocalUserId/.ssh/id_dsa.
+{info} |
+
+<a name="ReleasingOpenJPA1.0.xor1.1.x(OldSCPSteps)-ExposeacopyofknownhoststoMaven"></a>
+### Expose a copy of known hosts to Maven
+
+<table>
+<tr><th> 1 </td><td> From cygwin, ssh to people.apache.org, save the public key if
+prompted, and exit </th></tr>
+<tr><td> </td><td> cygwin will save the known hosts to your *\~/.ssh* folder, but the
+script cannot access it there (from Windows) </td></tr>
+<tr><th> 2 </td><td> From cygwin (not Windows) create another *.ssh* folder at (?) </th></tr>
+<tr><th> 3 </td><td> Copy the *known_hosts* file to the new *.ssh* folder </th></tr>
+</table>
+
+<a name="ReleasingOpenJPA1.0.xor1.1.x(OldSCPSteps)-Troubleshooting"></a>
+## Troubleshooting
+
+<a name="ReleasingOpenJPA1.0.xor1.1.x(OldSCPSteps)-SpaceCharacterinBuildRootPath"></a>
+### Space Character in Build Root Path
+
+<table>
+<tr><th> Description </td><td> If there are spaces in the path to the build root
+subdirectory, the maven task uses to generate the revision number for the
+org.apache.openjpa.revision.properties yields incorrect data. For example:
+</tr>
+<DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>org.apache.openjpa.revision.properties|borderStyle=solid</B></DIV><DIV class="codeContent panelContent">
+ revision.number=Type 'svnversion --help' for usage.
+ openjpa.version=1.0.1
+
+<table>
+<tr><th> Solution </td><td> Rename the path and remove all spaces. </th></tr>
+</table>
+
+<a name="ReleasingOpenJPA1.0.xor1.1.x(OldSCPSteps)-MerginglocalrepositorytoremoterepositoryinCygwin/Windows"></a>
+### Merging local repository to remote repository in Cygwin/Windows
+
+<table>
+<tr><th> Description </td><td> The "maven-stage-plugin" is very sensitive to the
+parameters being passed to it, i.e. the source and target URL properties.
+When this plugin is used under Cygwin, make sure the following practices
+are used:
+</tr>
+
+Problem symptom:
+
+ $ find . -name m2-repository -not -path "*openjpa-project*" \
+ -exec mvn -f "c:/tmp/maven-stage-plugin/pom.xml" stage:copy \
+ -Dsource=file://{}
+-Dtarget=scp://allee8285@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+\
+ -Dversion=1.0.1 \;
+ [INFO]
+ Scanning for projects...
+ [INFO]
+ Searching repository for plugin with prefix: 'stage'.
+ ........
+ [INFO]
+ Downloading file from the source repository:
+ [INFO]
+ ------------------------------------------------------------------------
+ [ERROR]
+ BUILD ERROR
+ [INFO]
+ ------------------------------------------------------------------------
+ [INFO]
+ Error copying repository from
+file://./openjpa-all/target/site/m2-repository to \
+
+scp://allee8285@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+
+* Quote and use the drive name in the path.
+Problem symptom:
+
+ $ find /cygdrive/c/OpenJPA.1.0.1.Release/1.0.1 -name m2-repository -not
+-path "*openjpa-project*" \
+ -exec mvn -f /cygwin/c/tmp/maven-stage-plugin/pom.xml stage:copy \
+ -Dsource=file://{}
+-Dtarget=scp://allee8285@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+\
+ -Dversion=1.0.1 \;
+ [INFO]
+ Scanning for projects...
+ [INFO]
+ Searching repository for plugin with prefix: 'stage'.
+ ........
+ [INFO]
+ Downloading file from the source repository:
+ [INFO]
+ ------------------------------------------------------------------------
+ [ERROR]
+ BUILD ERROR
+ [INFO]
+ ------------------------------------------------------------------------
+ [INFO]
+ Error copying repository from
+file:///cygdrive/c/OpenJPA.1.0.1.Release/1.0.1/openjpa-all/target/site/m2-repository
+to
+
+scp://allee8285@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+
+ Embedded error: Could not read from file:
+c:\cygdrive\c\OpenJPA.1.0.1.Release\1.0.1\openjpa-all\target\site\m2-repository
+ \cygdrive\c\OpenJPA.1.0.1.Release\1.0.1\openjpa-all\target\site\m2-repository
+(Access is denied.)
+
+* Specify the people.apache.org user id in the target property.
+Problem symptom:
+
+ $ find "c:/OpenJPA.1.0.1.Release/1.0.1" -name m2-repository -not -path
+"*openjpa-project*" \
+ -exec mvn -f "c:/tmp/maven-stage-plugin/pom.xml" stage:copy
+ -Dsource=file://{}
+-Dtarget=scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+\
+ -Dversion=1.0.1 \;
+ [INFO]
+ Scanning for projects...
+ [INFO]
+ Searching repository for plugin with prefix: 'stage'.
+ [INFO]
+
+----------------------------------------------------------------------------
+ ........
+ [INFO]
+ Downloading file from the source repository:
+/org/apache/openjpa/openjpa/maven-metadata.xml.sha1
+ [INFO]
+ Downloading metadata from the target repository.
+ Password:: *********
+ ........
+ Password:: *********
+ [INFO]
+ ------------------------------------------------------------------------
+ [ERROR]
+ BUILD ERROR
+ [INFO]
+ ------------------------------------------------------------------------
+ [INFO]
+ Error copying repository from
+file://c:/OpenJPA.1.0.1.Release/1.0.1/openjpa-all/target/site/m2-repository
+to \
+
+scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+
+<table>
+<tr><th> Solution </td><td> As recommended in the descriptions.
+</tr>
+{note}For example:
+
+ find "c:/OpenJPA.1.0.1.Release/1.0.1" -name m2-repository -not -path
+"*openjpa-project*" \
+ -exec mvn -f "c:/tmp/maven-stage-plugin/pom.xml" stage:copy \
+ -Dsource=file://{} \
+
+-Dtarget=scp://allee8285@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+\
+ -Dversion=1.0.1 \;
+
+<a name="ReleasingOpenJPA1.0.xor1.1.x(OldSCPSteps)-Cygwin/WindowsFilePath"></a>
+### Cygwin/Windows File Path
+
+<table>
+<tr><th> Description </td><td> For Cygwin/Windows user: file and folder path names using
+drive identifier (e.g. *C:\OpenJPA Release\1.0.1\* ) in commands can be
+expressed as */cygwin/c/OpenJPA Release/1.0.1/*. This form of path name
+specification may have inconsistent and undesirable behaviors.</th></tr>
+<tr><th> Solution </td><td> Consistently use the following naming conventions:
+</tr>
+* Continue to use the Windows form of path name, e.g. *C:\a\b\c*
+* Use *'/'* instead of *'\'* character as file separator, e.g.
+*C:/a/b/c*
+* Quote all path name using *'"'* character, e.g. "*C:/a/b/c*"
+* Avoid using space characters in path name, e.g.
+"*C:/OpenJPA.Release/1.0.1*"
+ ||
+</table>
+
+<a name="ReleasingOpenJPA1.0.xor1.1.x(OldSCPSteps)-"Toomanyunapprovedlicenses:""></a>
+### "Too many unapproved licenses:"
+
+<table>
+<tr><th> Description </td><td> Encounter the "Too many unapproved licenses:" message
+while running the "license-verify-profile" profile in "{{mvn deploy
+site...}}" step. This is caused by extra artifacts in the build tree that
+the license verification plugin does not recognized. Examples of these
+artifacts are:
+</tr>
+1. Eclipse control files, .classpath, .project
+1. User created log files ||
+<tr><th> Solution </td><td> Avoid the followings:
+</tr>
+1. Don't use Eclipse's svn plugin to "Check out" files to a Eclipse project.
+Simply use the svn command, as described in the release instructions.
+1. Don't create, directly or indirectly, any files under the release build
+tree.
+ ||
+</table>
+
+<a name="ReleasingOpenJPA1.0.xor1.1.x(OldSCPSteps)-Resources"></a>
+## Resources
+
+* Apache Apache [Release FAQ](http://www.apache.org/dev/release.html)
+* [Signing Releases](http://apache.org/dev/release-signing.html)
+* [Wendy's notes on Release Signing](http://wiki.wsmoak.net/cgi-bin/wiki.pl?ReleaseSigning)
+* Apache [Mirroring Guidelines](http://apache.org/dev/mirrors.html)
+* Struts [Release Instructions](http://cwiki.apache.org/WW/creating-and-signing-a-distribution.html)
+ (upon which these instructions are based)
+ </div>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <div class="bottom_red_bar"></div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="black_box">
+ <div class="footer">
+ <div class="footer_l">
+ <div class="footer_r">
+ <div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="design_attribution">
+ Copyright (C) 2006,2012 The Apache Software Foundation. Licensed under <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License 2.0</a>.<br />
+ Apache, the Apache feather logo and OpenJPA are trademarks of The Apache Software Foundation.<br />
+ Other names may be trademarks of their respective owners.<br />
+ </div>
+
+ <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
+ </script>
+ <script type="text/javascript">
+ _uacct = "UA-1940143-1";
+ urchinTracker();
+ </script>
+
+ </body>
+</html>
Added: websites/staging/openjpa/trunk/content/releasing-openjpa-1.2.x-(old-scp-steps).html
==============================================================================
--- websites/staging/openjpa/trunk/content/releasing-openjpa-1.2.x-(old-scp-steps).html (added)
+++ websites/staging/openjpa/trunk/content/releasing-openjpa-1.2.x-(old-scp-steps).html Sun Dec 9 13:13:35 2012
@@ -0,0 +1,851 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+<html lang="en">
+ <head>
+ <META http-equiv="Content-Type" content="text/html;charset=UTF-8" />
+ <link href="http://openjpa.apache.org/styles/site.css" rel="stylesheet" type="text/css"/>
+ <!-- <link href="http://openjpa.apache.org/styles/type-settings.css" rel="stylesheet" type="text/css"/> -->
+ <link href="./css/type-settings.css" rel="stylesheet" type="text/css"/>
+ <LINK rel="schema.DC" href="http://purl.org/DC/elements/1.0/">
+ <META name="Description" content="Apache OpenJPA -- Releasing OpenJPA 1.2.x (Old SCP Steps)
" />
+ <META name="Keywords" content="Apache OpenJPA, JPA, JPA 1.0, JSR-220, JPA2, JPA 2.0, JSR-317, " />
+ <META name="Owner" content="dev@openjpa.apache.org" />
+ <META name="Robots" content="index, follow" />
+ <META name="Security" content="Public" />
+ <META name="Source" content="wiki template" />
+ <META name="DC.Date" scheme="iso8601" content="2010-08-11" />
+ <META name="DC.Language" scheme="rfc1766" content="en" />
+ <META name="DC.Rights" content="Copyright © 2006,2010 The Apache Software Foundation" />
+ <META http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))'/>
+
+ <title>
+ Apache OpenJPA --
+ </title>
+ </head>
+ <body>
+ <div class="white_box">
+ <div class="header">
+ <div class="header_l">
+ <div class="header_r">
+ </div>
+ </div>
+ </div>
+ <div class="content">
+ <div class="content_l">
+ <div class="content_r">
+ <div>
+ <!-- Banner -->
+ <TABLE valign="top" border="0" cellspacing="0" cellpadding="5" width="100%" background="images/header-bg3.png">
+ <TR>
+ <TD valing="top" align="left">
+ <A href="http://openjpa.apache.org/"><IMG src="images/openjpa-logo.png" border="0" alt="OpenJPA Logo"></A>
+ </TD>
+ <TD width="100%">
+
+ </TD>
+ <TD valing="top" align="right">
+ <A href="http://www.apache.org/"><IMG src="images/asf_logo_wide2.png" border="0" alt="ASF Logo"></A>
+ </TD>
+ </TR>
+ </TABLE>
+
+ <!-- Navigation Bar -->
+ <div class="bottom_red_bar">
+ <div id="site-breadcrumbs">
+ <!-- Breadcrumbs --
+ <a href="/">Home</a> » <a href="/releasing-openjpa-1.2.x-(old-scp-steps).html">Releasing OpenJPA 1.2.x (Old SCP Steps)
</a>
+ -- Breadcrumbs -->
+ </div>
+ </div>
+
+ <!-- Content -->
+ <table border="0">
+ <tbody>
+ <tr>
+ <td valign="top">
+ <div class="navigation">
+ <div class="navigation_top">
+ <div class="navigation_bottom">
+ <!-- NavigationBar -->
+ <h3><a name="SideNav-Overview"></a><a href="overview.html" title="Overview">Overview</a></h3>
+
+ <ul class="alternate" type="square">
+ <li><a href="quick-start.html" title="Quick Start">Quick Start</a></li>
+ <li><a href="documentation.html" title="Documentation">Documentation</a></li>
+ <li><a href="downloads.html" title="Downloads">Downloads</a></li>
+ <li><a href="site-index.html" title="Site Index">Site Index</a></li>
+ <li><a href="license.html" title="License">License</a></li>
+ <li><a href="privacy-policy.html" title="Privacy Policy">Privacy Policy</a></li>
+ </ul>
+
+ <h3><a name="SideNav-Community"></a><a href="community.html" title="Community">Community</a></h3>
+
+ <ul class="alternate" type="square">
+ <li><a href="index.html#Index-eventsandnews" title="Events and News">Events and News</a></li>
+ <li><a href="found-a-bug.html" title="Found a Bug">Found a Bug</a>?</li>
+ <li><a href="get-involved.html" title="Get Involved">Get Involved</a></li>
+ <li><a href="mailing-lists.html" title="Mailing Lists">Mailing Lists</a></li>
+ <li><a href="committers.html" title="Committers">Committers</a></li>
+ <li><a href="integration.html" title="Integration">Integration</a></li>
+ <li><a href="powered-by.html" title="Powered By">Powered By</a></li>
+ <li><a href="thanks.html" title="Thanks">Thanks</a></li>
+ </ul>
+
+
+ <h3><a name="SideNav-Development"></a><a href="development.html" title="Development">Development</a></h3>
+
+ <ul class="alternate" type="square">
+ <li><a href="http://issues.apache.org/jira/browse/OPENJPA" class="external-link" rel="nofollow">Issue Tracker</a></li>
+ <li><a href="source-code.html" title="Source Code">Source Code</a></li>
+ <li><a href="testing.html" title="Testing">Testing</a></li>
+ <li><a href="tools.html" title="Tools">Tools</a></li>
+ <li><a href="samples.html" title="Samples">Samples</a></li>
+ <li><a href="release-management.html" title="Release Management">Release Management</a></li>
+ </ul>
+
+ <h3>Search</h3>
+
+ <div style="padding: 5px 5px 0px 25px;">
+ <form action="http://www.google.com/search" method="get" style="font-size: 10px;">
+ <input name="ie" type="hidden" value="UTF-8">
+ <input name="oe" type="hidden" value="UTF-8">
+ <input maxlength="255" name="q" size="9" type="text" value=""><br><br>
+ <input name="btnG" type="submit" value="Google">
+ <input name="domains" type="hidden" value="openjpa.apache.org">
+ <input name="sitesearch" type="hidden" value="openjpa.apache.org">
+ </form>
+ </div>
+ </div>
+ </div>
+ </div>
+ </td>
+ <td valign="top" width="100%" style="overflow:hidden;">
+ <div class="wiki-content">
+ <p>{excerpt:hidden=true}Instructions for creating an official OpenJPA
+release{excerpt}
+<a name="ReleasingOpenJPA1.2.x(OldSCPSteps)-ReleasingOpenJPA"></a></p>
+<h1 id="releasing-openjpa">Releasing OpenJPA</h1>
+<p>These instructions guide the release manager through the steps of making an
+official OpenJPA release.</p>
+<p><em>Work in progress. Times are just guesses and some information may be
+missing.</em></p>
+<p><a name="ReleasingOpenJPA1.2.x(OldSCPSteps)-Prerequisites"></a></p>
+<h2 id="prerequisites">Prerequisites</h2>
+<p>// TODO MDD Still may need some work...</p>
+<ol>
+<li>You should read the <a href="openjpa-release-policy.html">OpenJPA Release Policy</a>
+ to decide on the name of the new release, based on the content.</li>
+<li>You should read the Apache <a href="http://www.apache.org/dev/release.html">Release FAQ</a></li>
+<li>You must have shell access to people.apache.org</li>
+<li>You must have the following utilities installed on your local machine and
+available in your path:</li>
+<li>
+<ul>
+<li>Java SE 5.0 (for 1.2.x and 1.3.x) or Java SE 6 (for 2.0.x) (prefer Sun
+JDK over IBM JDK)</li>
+</ul>
+</li>
+<li>
+<ul>
+<li><a href="http://maven.apache.org/">Maven 2</a>
+ (at least version 2.0.10)</li>
+</ul>
+</li>
+<li>
+<ul>
+<li><a href="http://www.openssh.com/">ssh</a>
+ (cygwin covers this on Windows)</li>
+</ul>
+</li>
+<li>
+<ul>
+<li><a href="http://www.gnupg.org/">gnupg</a>
+ (cygwin covers this on Windows)</li>
+</ul>
+</li>
+<li>For Windows users, install <a href="http://cygwin.com/">Cygwin</a>
+ in addition to the above utilities</li>
+<li>
+<ul>
+<li>Make sure the Net/openssh and Utils/gnupg packages are installed that
+come with Cygwin installation. </li>
+</ul>
+</li>
+</ol>
+<p><a name="ReleasingOpenJPA1.2.x(OldSCPSteps)-Tasksthatneedtobeperformedforeachrelease"></a></p>
+<h2 id="tasks-that-need-to-be-performed-for-each-release">Tasks that need to be performed for each release</h2>
+<p><em>The example below uses 1.2.x as the new branch and 1.2.0 as the new
+release.</em></p>
+<ul>
+<li>Cleanup JIRA so the Fix Version in issues resolved since the last release
+includes this release version correctly.</li>
+<li>Update the files in openjpa-project -
+<strong> Update the CHANGES.txt and RELEASE_NOTES.html based on the Text and HTML
+release reports from JIRA.
+</strong> Review and update BUILDING.txt if needed.</li>
+<li>Stage any Roadmap or Release landing pages on the wiki.</li>
+<li>Use "mvn rat:check" to verify the source has the required headers before
+trying to release.</li>
+<li>
+<p>Perform a full build (IANAL + tests) and TCK runs before trying to
+release.</p>
+</li>
+<li>
+<p>set MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=256m (especially for Java SE 6)</p>
+</li>
+<li>
+<p>Use Sun JDK (if possible)
+** If using IBM JDK, then also set the system property test.jvm.arguments
+to -Xdump:none (Avoids OOM heap dumps on selected tests. These extra files
+throw off the rat:check processing.) For example,
+{code:none}
+mvn -Dtest.jvm.arguments="-Xdump:none" ...</p>
+<ul>
+<li>On Windows, use a cygwin window (vs a standard DOS prompt window) for the
+Release processing.||
+|| Monday, 12:01 \ | ??? For new major releases (like 2.0.0) create a
+sub-branch off of the parent branch from which to make the release.
+Releasing from a branch will allow any cosmetic changes that need to be
+made for the release to be approved to be done without preventing other
+more disruptive advances in the trunk from potentially causing problems
+with the release. A branch can be made by running: \
+{code:none}
+$ mvn release:branch -DbranchName=1.2.x</li>
+</ul>
+</li>
+<li>
+<p>Do not use Eclipse to do the checkout. The extra dot (.) files created
+by Eclipse throws off the rat:check processing.
+{code:none} $ svn checkout
+https://svn.apache.org/repos/asf/openjpa/branches/1.2.x 1.2.x
+$ cd 1.2.x {code}||</p>
+</li>
+</ul>
+<table>
+<tr></tr>
+
+{code:none} $ svn commit -m "updating text files for 1.2.0 release"
+
+ || Monday, 12:11 \\ | Do a dry run of the release plugin. The dry run will
+not commit any changes back to SVN and gives you the opportunity to verify
+that the release process will complete as expected. You will be prompted
+for the following information :
+ # The new release number (default 1.2.0)
+ # The SCM tag (default apache-openjpa-1.2.0) *this should be changed to
+just 1.2.0
+ # The new development version (default 1.2.1)
+ # _optional_ if you have not specified a GPG passphrase in settings.xml you
+will be prompted for it.
+ {code:none}$ mvn -Prelease,docbook-profile release:prepare -DdryRun=true
+ <snip>
+ [INFO]
+ [release:prepare]
+ [INFO]
+ Verifying that there are no local modifications...
+ [INFO]
+ Executing: svn --non-interactive status
+ [INFO]
+ Working directory: /home/mikedd/workspaces/temp/jpadev/branches/1.0.x
+ [INFO]
+ Checking dependencies and plugins for snapshots ...
+ What is the release version for "OpenJPA"?
+(org.apache.openjpa:openjpa-parent) 1.2.0: :
+ What is SCM release tag or label for "OpenJPA"?
+(org.apache.openjpa:openjpa-parent) openjpa-parent-1.2.0: : 1.2.0
+ What is the new development version for "OpenJPA"?
+(org.apache.openjpa:openjpa-parent) 1.2.1-SNAPSHOT: :
+ {code} ||
+ || Monday, 12:30 \\ | Validate that the release process completed as
+expected. The release plugin will create pom.xml.tag files which contain
+the changes that would have been committed to SVN. The only differences
+between pom.xml.tag and it's corresponding pom.xml file should be the
+version number. If other formatting changes have been made you should
+rollback the release and commit the changes manually.
+ {code:none}$ mvn -Prelease,docbook-profile release:rollback
+ # make changes
+ $ svn commit -m "fixing formatting for 1.2.0 release" {code} ||
+ || Monday, 12:31 \\ | Assuming the .tag files look OK you may proceed and
+do any other validation you feel necessary. The following list may be
+helpful
+ * verify signatures [Verifying release signatures]
+ * run examples. [Running OpenJPA Examples]
+ * if you have access to the TCK, run it [Running the TCK]
+||
+ || Monday, 12:52 \\ | Prepare the release. You'll be prompted for the
+version information and optionally your GPG passphrase again.
+ {code:none} $ mvn -Dmaven.test.execute=false -Prelease release:prepare
+{code}
+ For the 2.0.x code, different steps are required as there are problems with
+the maven-jar-plugin and maven-release-plugin when using the test-jar goal.
+ See [http://jira.codehaus.org/browse/MJAR-68]
+ and [http://jira.codehaus.org/browse/MRELEASE-285]
+.
+ {code:none} $ mvn -DskipTests=true -Prelease release:prepare
+-DpreparationGoals="clean install"
+ $ mvn clean install -Dtest=false -DfailIfNoTests=false
+-Dmaven.test.execute=false
+ $ mvn -DskipTests=true -Prelease release:prepare -DpreparationGoals="clean
+install" {code} ||
+ || Monday, 13:12 \\ | Check release.properties and make sure that the scm
+properties have the right version. Sometimes the scm location can be the
+previous version not the next version. For example if the new version is
+1.2.2 you shouldn't see 1.2.1 in the file. \\
+ {note}Backup (zip or tar) your local directory in case you need to rollback
+the release.{note} ||
+ || Monday, 13:15 \\ | Perform the release. This step will create a maven
+repository for use in testing on
+people.apache.org:/home/userName/public_html/openjpa/newVersion. You will
+may be prompted for your people.apache.org password several times if you
+have not added a ssh key to .authorized_keys. [#One time setup#people.apache.org]
+.
+ {code:none}$ mvn -Prelease,docbook-profile release:perform {code}
+ For the 2.0.x code, you'll need additional parameters, due to the test-jar
+issues.
+ {code:none}$ mvn -Prelease,docbook-profile,test-derby release:perform
+{code}
+ {info} If your local OS userid doesn't match your Apache userid, then
+you'll have to set -Duser.name=<your_apache_id> on the cmdline and/or
+update your release profile in settings.xml {info} ||
+ || Monday, 13:40 \\ | Create and upload the site. This step also uploads
+data to people.apache.org.
+ For 1.x releases:
+ {code:none}
+ $ cd target/checkout
+ $ mvn -Prelease,docbook-profile site site:deploy {code}
+ {warning} *For 2.x releases*, this step is not needed, as the
+maven-release-plugin is configured with goals "deploy site site:deploy"
+{warning} ||
+ || Monday, 13:41 \\ | Unzip the binary archive the staging site directory
+ {code:none}
+ # ssh to people.apache.org
+ $ cd ~/public_html/openjpa/${pom.version}/staging-site
+ $ unzip -qq
+apache-openjpa/downloads/apache-openjpa-${pom.version}-binary.zip
+
+Verify that the HTML links in staging-site/index.html are correct (usually
+only the downloads and docs links need to be updated to be prefixed with
+apache-openjpa/)
+
+See [http://people.apache.org/~henkp/repo/faq.html](http://people.apache.org/~henkp/repo/faq.html)
+ and [http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig]
+ {note}
+
+{code:none} $ mvn stage:copy
+-Dsource="http://people.apache.org/~mikedd/openjpa/1.2.0/staging-repo" \
+
+-Dtarget="scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository"
+\
+ -Dversion=1.2.0 \
+ -DtargetRepositoryId=apache.releases
+
+ After the stage plugin completes it's a good idea to check the permissions
+on the file system.
+
+$ ssh people.apache.org
+$ cd
+/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/openjpa/
+$ ls -l openjpa-examples/1.2.0
+
+1. if you see something like the following you probably need to change the
+permissions.
+1. *-rw-r--r--* 1 mikedd apcvs 59162 Jul 23 09:34
+openjpa-examples-1.2.0-javadoc.jar
+
+$ for file in `find
+/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/openjpa/
+-type d -iname '1.2.0'`\
+ do \
+ chmod -R g+w ${file} \
+ done
+
+$ ls -l openjpa-examples/1.2.0
+
+1. Now it should look something like this
+1. *-rw-rw--r--* 1 mikedd apcvs 59162 Jul 23 09:34
+openjpa-examples-1.2.0-javadoc.jar
+
+ || Thursday, 14:00 \\ | Copy build artifacts to the openjpa/builds location
+on people.apache.org.
+ {code:none}# ssh to people.apache.org
+ $ cp -r ~/public_html/openjpa/1.2.0/staging-site/
+/www/openjpa.apache.org/builds/1.2.0
+ $ chmod -R g+w /www/openjpa.apache.org/builds/1.2.0
+ # verify that /www/openjpa.apache.org/builds/1.2.0/docs/manual is populated
+correctly by comparing it to a previous release.
+ $ rm /www/openjpa.apache.org/docs/latest
+ $ ln -fvs ../builds/1.2.0/apache-openjpa/docs/
+/www/openjpa.apache.org/docs/latest {code} ||
+ || Thursday, 14:10 \\ | Copy the distribution files to dist on
+people.apache.org.
+ {code:none}
+ # ssh to people.apache.org
+
+ # verify that md5 and sha1 files were generated for the download artifacts
+ ls /www/openjpa.apache.org/builds/1.2.0/apache-openjpa/downloads/*.md5
+ ls /www/openjpa.apache.org/builds/1.2.0/apache-openjpa/downloads/*.sha1
+
+ # if no md5 and sha1 files are present, generate them.
+ # Alternatively you can copy the artifacts from the staging-repo directory
+the checksums are generated there.
+ for file in `ls . `
+ do
+ md5 -q ${file} > ${file}.md5
+ sha1 -q ${file} > ${file}.sha1
+ done
+
+ mkdir /www/www.apache.org/dist/openjpa/1.2.0
+ cp -r /www/openjpa.apache.org/builds/1.2.0/apache-openjpa/downloads/*
+/www/www.apache.org/dist/openjpa/1.2.0
+ chgrp -R openjpa /www/www.apache.org/dist/openjpa/1.2.0
+ chmod -R g+w /www/www.apache.org/dist/openjpa/1.2.0
+
+ # remove the previous version from /dist. Ie if you're publishing 1.2.1 you
+would remove 1.2.0.
+ # For this example we wouldn't remove anything, but for the next release
+(1.2.1) we'd do the following :
+ $ rm -Rf /www/openjpa.apache.org/dist/openjpa/1.2.0
+
+<table>
+<tr><th> Thursday, 14:15 </td><td> Update the [JIRA versions ](-https://issues.apache.org/jira/secure/project/manageversions.jspa?pid=12310351.html)
+ page to mark the version as "released", and set the date to the date that
+the release was approved. You may also need to make a new release entry for
+the subsequent release.</th></tr>
+<tr><th> Friday, 14:15 </td><td> After the mirrors have had time to update (24 hours to
+be on the safe side) update the [Downloads](downloads.html)
+ and [Documentation]
+ pages with the new release </th></tr>
+<tr><th> Friday, 14:15 </td><td> Make a [news announcement](http://cwiki.apache.org/confluence/pages/createblogpost.action?spaceKey=openjpa)
+ on the OpenJPA wiki. {info}Once the news item is made, it won't show up on
+the [front page</td><td>http://cwiki.apache.org/openjpa/]
+ unless you make some minor edit to the containing page (e.g., adding a
+newline somewhere).{info} </th></tr>
+<tr><th> Friday, 14:15 </td><td> Make an announcement about the release on the [mailto:users@openjpa.apache.org](mailto:users@openjpa.apache.org.html)
+ list (and, for major releases, on the [mailto:announce@apache.org]
+ list as per [the Apache Announcement Mailing Lists page</td><td>http://www.apache.org/foundation/mailinglists.html#foundation-announce]
+). The announcement might look something like [this</td><td>http://www.nabble.com/-ANNOUNCE--Apache-OpenJPA-1.0.0-released-p12397604.html]
+. </th></tr>
+<tr><th> Friday, 14:20 </td><td> Make an announcement for the [freshmeat.net OpenJPA project](http://freshmeat.net/projects/openjpa/)
+ (optional) </th></tr>
+<tr><th> Friday, 14:30 </td><td> Have a beer and enjoy your weekend while the world's
+grateful programmers revel in yet another high-quality release of Apache
+OpenJPA! </th></tr>
+</table>
+
+<a name="ReleasingOpenJPA1.2.x(OldSCPSteps)-Onetimesetup"></a>
+## One time setup
+
+These setup steps only need to be performed on a particular machine once.
+{info}Developers using Linux workstations can skip over the references to
+Cygwin. If using Windows, install cygwin, including *Utils/gnupg* and
+*Net/openssh* packages.
+{info}
+
+<a name="ReleasingOpenJPA1.2.x(OldSCPSteps)-CreateandinstallaSSHkey"></a>
+### Create and install a SSH key
+
+<table>
+<tr><th> 1 </td><td> Open a shell window. If using Windows, open a cygwin window. </th></tr>
+<tr><th> 2 </td><td> Use ssh-keygen to create an SSH key.
+</tr>
+{note}Follow the latest steps and guides on the ASF website at [http://www.apache.org/dev/openpgp.html#generate-key](http://www.apache.org/dev/openpgp.html#generate-key)
+ as you need to disable using SHA1 and new keys should be 4096 bits.{note}
+{code:none}
+$ ssh-keygen -t dsa
+
+ * Program defaults should be fine. No passphrase is required for the ssh
+key generation. The keys will be saved in ~/.ssh/id_dsa (private) and
+~/.ssh/id_dsa.pub (public).
+ {info} See [Authenticating By Public Key (OpenSSH)|http://www.networknewz.com/networknewz-10-20030707AuthenticatingbyPublicKeyOpenSSH.html]
+ for a good description on why and how to perform this task.
+ {info} ||
+ || 3 | {{scp}} your SSH public key ~/.ssh/id_dsa.pub created in last step
+to ~/id_dsa.pub on people.apache.org.
+ {code:none}
+ $ cd ~/.ssh
+ $ scp id_dsa.pub <your userid>@people.apache.org:id_dsa.pub
+ $ You will be prompted for your password.
+
+<table>
+<tr><th> 4 </td><td> Use ssh to login to people.apache.org
+</tr>
+{code:none}
+$ cd ~
+$ ssh <your userid>@people.apache.org
+
+ * At this point, you will still be prompted for your password. ||
+ || 5 | Create a ~/.ssh folder in your home directory on people.apache.org
+and change its file mode to 700.
+ {code:none}
+ $ mkdir ~/.ssh
+ $ chmod 700 ~/.ssh
+
+<table>
+<tr><th> 6 </td><td> Move or append ~/id_dsa.pub to ~/.ssh/authorized_keys and change its
+file mode to 600.
+</tr>
+{code:none}
+$ mv ~/id_dsa.pub ~/.ssh/authorized_keys
+$ chmod 600 ~/.ssh/authorized_keys
+
+ {info}
+ * Each public key in the {{authorized_keys}} spans only one line.
+ ** For example: "{{ssh-dss AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA==
+dsa-key-20071107}}"
+ * '#' in the first column is a comment line.
+ {info} ||
+ || 7 | Exit out of this ssh session. ||
+ || 8 | Start a new ssh session. No login should be required this time due
+to the private ssh key on your local box matching up with the public ssh
+key in your home directory (~/.ssh).
+ {code:none}
+ $ ssh <your userid>@people.apache.org
+
+{info}
+If you are still prompted for a password, then you have not set up the ssh
+keys properly. Review the steps above and ensure that all of the steps
+were followed properly. Or, maybe the instructions are still not quite
+right and they still need some adjusting. In that case, please update the
+instructions accordingly. :-)
+{info}
+<table>
+<tr></tr>
+</table>
+
+<a name="ReleasingOpenJPA1.2.x(OldSCPSteps)-CreateaGPGkey"></a>
+### Create a GPG key
+
+<table>
+<tr><th> 1 </td><td> Open a shell window. If using Windows, open a cygwin window. </th></tr>
+<tr><th> 2 </td><td> Generate a key-pair with gpg, using default key kind ("DSA and
+Elgamal") and ELG-E keys size (2048).
+</tr>
+{code:none}
+$ gpg --gen-key
+
+ * The program's default values should be fine. For the "Real Name" enter
+your full name (ie. Stan Programmer). For the "e-mail address" enter your
+apache address (ie. sprogrammer@apache.org). You will also be required to
+enter a "passphrase" for the GPG key generation. Keep track of this as you
+will need this for the Release processing.
+ {info}
+ * The generated keys are stored in $HOME/.gnupg or %HOME%\Application
+Data\gnupg subdirectory.
+ * Save the content in this subdirectory to a safe media. This contains your
+private key used to sign all the OpenJPA release materials.
+ {info} ||
+ || 3 | Backup your cygwin home directory to another media ||
+ || 4 | Add your public key to {{[https://svn.apache.org/repos/asf/openjpa/site/docs/KEYS]
+}} and {{http://www.apache.org/dist/openjpa/KEYS}}. See the commands
+describe at the beginning of this KEYS file to perform this task. The gpg
+key-pair is used to sign the published artifacts for the OpenJPA releases.
+ {code:none}
+ $ gpg --list-sigs <Real Name> && gpg --armor -- export <Real Name>
+
+{info}The {{[https://svn.apache.org/repos/asf/openjpa/site/docs/KEYS](https://svn.apache.org/repos/asf/openjpa/site/docs/KEYS)
+}} file is updated via normal svn commit procedures. How the
+*http://www.apache.org/dist/openjpa/KEYS* file gets updated is still a
+mystery to me...
+{info} ||
+<table>
+<tr><th> 5 </td><td> Following the instructions in [http://people.apache.org/~henkp/trust/](http://people.apache.org/~henkp/trust/)
+ and ask someone in the OpenJPA project to sign your public key. </th></tr>
+<tr><th> 6 </td><td> Submit your public key to a key server. E.g. [http://pgp.surfnet.nl:11371/](http://pgp.surfnet.nl:11371/)
+ or [http://pgp.mit.edu/]
+</th></tr>
+</table>
+
+<a name="ReleasingOpenJPA1.2.x(OldSCPSteps)-UpdateMavensettingsforourservers"></a>
+### Update Maven settings for our servers
+
+<table>
+<tr><th> 1 </td><td> Create a settings.xml under .m2 (in your Document and Settings
+folder in Windows) </th></tr>
+<tr><td> </td><td> {code:xml</td><td>title=settings.xml</td><td>borderStyle=solid}
+</tr>
+<settings xmlns="http://maven.apache.org/POM/4.0.0"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
+http://maven.apache.org/xsd/settings-1.0.0.xsd">
+ <servers>
+ <server>
+ <id>people.apache.org</id>
+ <username>$USERNAME</username>
+ <privateKey>$PATH_TO_PRIVATE_KEY</privateKey>
+ <directoryPermissions>775</directoryPermissions>
+ <filePermissions>644</filePermissions>
+ </server>
+ </servers>
+</settings>
+
+ {info}
+ * {{$USERNAME}} is the remote username on people.apache.org, not your local
+userid.
+ * {{$PATH_TO_PRIVATE_KEY}} is the path to the private key generated for
+ssh. E.g. /home/yourLocalUserId/.ssh/id_dsa. For Windows' cygwin users,
+you will need to enter the full cygwin path:
+/cygdrive/c/cygwin/home/yourLocalUserId/.ssh/id_dsa.
+ * You can also enter a PGP passphrase stanza: <passphrase>..</passphrase>.
+ If you don't use this in your settings.xml file, then you will be prompted
+for it during the Release processing.
+ {info} |
+
+ h3. Expose a copy of known hosts to Maven
+ {info}
+ Is this step even necessary? Due to the question mark below without an
+explanation of the new location for this alternate .ssh folder, I never
+performed these steps. And, the release process still seemed to work okay
+for me... The next person to use these instructions can verify whether any
+tricks had to be played with the .ssh folders...
+ {info}
+
+ || 1 | From cygwin, ssh to people.apache.org, save the public key if
+prompted, and exit ||
+ | | cygwin will save the known hosts to your {{\~/.ssh}} folder, but the
+script cannot access it there (from Windows) |
+ || 2 | From cygwin (not Windows) create another {{.ssh}} folder at (?) ||
+ || 3 | Copy the {{known_hosts}} file to the new {{.ssh}} folder ||
+
+ h2. Troubleshooting
+
+ h3. Space Character in Build Root Path
+
+ || Description | If there are spaces in the path to the build root
+subdirectory, the maven task uses to generate the revision number for the
+org.apache.openjpa.revision.properties yields incorrect data. For example:
+ {code:title=org.apache.openjpa.revision.properties|borderStyle=solid}
+ revision.number=Type 'svnversion --help' for usage.
+ openjpa.version=1.0.1
+
+<table>
+<tr><th> Solution </td><td> Rename the path and remove all spaces. </th></tr>
+</table>
+
+<a name="ReleasingOpenJPA1.2.x(OldSCPSteps)-MerginglocalrepositorytoremoterepositoryinCygwin/Windows"></a>
+### Merging local repository to remote repository in Cygwin/Windows
+
+<table>
+<tr><th> Description </td><td> The "maven-stage-plugin" is very sensitive to the
+parameters being passed to it, i.e. the source and target URL properties.
+When this plugin is used under Cygwin, make sure the following practices
+are used:
+</tr>
+
+Problem symptom:
+
+ $ find . -name m2-repository -not -path "*openjpa-project*" \
+ -exec mvn -f "c:/tmp/maven-stage-plugin/pom.xml" stage:copy \
+ -Dsource=file://{}
+-Dtarget=scp://allee8285@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+\
+ -Dversion=1.0.1 \;
+ [INFO]
+ Scanning for projects...
+ [INFO]
+ Searching repository for plugin with prefix: 'stage'.
+ ........
+ [INFO]
+ Downloading file from the source repository:
+ [INFO]
+ ------------------------------------------------------------------------
+ [ERROR]
+ BUILD ERROR
+ [INFO]
+ ------------------------------------------------------------------------
+ [INFO]
+ Error copying repository from
+file://./openjpa-all/target/site/m2-repository to \
+
+scp://allee8285@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+
+* Quote and use the drive name in the path.
+Problem symptom:
+
+ $ find /cygdrive/c/OpenJPA.1.0.1.Release/1.0.1 -name m2-repository -not
+-path "*openjpa-project*" \
+ -exec mvn -f /cygwin/c/tmp/maven-stage-plugin/pom.xml stage:copy \
+ -Dsource=file://{}
+-Dtarget=scp://allee8285@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+\
+ -Dversion=1.0.1 \;
+ [INFO]
+ Scanning for projects...
+ [INFO]
+ Searching repository for plugin with prefix: 'stage'.
+ ........
+ [INFO]
+ Downloading file from the source repository:
+ [INFO]
+ ------------------------------------------------------------------------
+ [ERROR]
+ BUILD ERROR
+ [INFO]
+ ------------------------------------------------------------------------
+ [INFO]
+ Error copying repository from
+file:///cygdrive/c/OpenJPA.1.0.1.Release/1.0.1/openjpa-all/target/site/m2-repository
+to
+
+scp://allee8285@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+
+ Embedded error: Could not read from file:
+c:\cygdrive\c\OpenJPA.1.0.1.Release\1.0.1\openjpa-all\target\site\m2-repository
+ \cygdrive\c\OpenJPA.1.0.1.Release\1.0.1\openjpa-all\target\site\m2-repository
+(Access is denied.)
+
+* Specify the people.apache.org user id in the target property.
+Problem symptom:
+
+ $ find "c:/OpenJPA.1.0.1.Release/1.0.1" -name m2-repository -not -path
+"*openjpa-project*" \
+ -exec mvn -f "c:/tmp/maven-stage-plugin/pom.xml" stage:copy
+ -Dsource=file://{}
+-Dtarget=scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+\
+ -Dversion=1.0.1 \;
+ [INFO]
+ Scanning for projects...
+ [INFO]
+ Searching repository for plugin with prefix: 'stage'.
+ [INFO]
+
+----------------------------------------------------------------------------
+ ........
+ [INFO]
+ Downloading file from the source repository:
+/org/apache/openjpa/openjpa/maven-metadata.xml.sha1
+ [INFO]
+ Downloading metadata from the target repository.
+ Password:: *********
+ ........
+ Password:: *********
+ [INFO]
+ ------------------------------------------------------------------------
+ [ERROR]
+ BUILD ERROR
+ [INFO]
+ ------------------------------------------------------------------------
+ [INFO]
+ Error copying repository from
+file://c:/OpenJPA.1.0.1.Release/1.0.1/openjpa-all/target/site/m2-repository
+to \
+
+scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+
+<table>
+<tr><th> Solution </td><td> As recommended in the descriptions.
+</tr>
+{note}For example:
+
+ find "c:/OpenJPA.1.0.1.Release/1.0.1" -name m2-repository -not -path
+"*openjpa-project*" \
+ -exec mvn -f "c:/tmp/maven-stage-plugin/pom.xml" stage:copy \
+ -Dsource=file://{} \
+
+-Dtarget=scp://allee8285@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
+\
+ -Dversion=1.0.1 \;
+
+<a name="ReleasingOpenJPA1.2.x(OldSCPSteps)-Cygwin/WindowsFilePath"></a>
+### Cygwin/Windows File Path
+
+<table>
+<tr><th> Description </td><td> For Cygwin/Windows user: file and folder path names using
+drive identifier (e.g. *C:\OpenJPA Release\1.0.1\* ) in commands can be
+expressed as */cygwin/c/OpenJPA Release/1.0.1/*. This form of path name
+specification may have inconsistent and undesirable behaviors.</th></tr>
+<tr><th> Solution </td><td> Consistently use the following naming conventions:
+</tr>
+* Continue to use the Windows form of path name, e.g. *C:\a\b\c*
+* Use *'/'* instead of *'\'* character as file separator, e.g.
+*C:/a/b/c*
+* Quote all path name using *'"'* character, e.g. "*C:/a/b/c*"
+* Avoid using space characters in path name, e.g.
+"*C:/OpenJPA.Release/1.0.1*"
+ ||
+</table>
+
+<a name="ReleasingOpenJPA1.2.x(OldSCPSteps)-"Toomanyunapprovedlicenses:""></a>
+### "Too many unapproved licenses:"
+
+<table>
+<tr><th> Description </td><td> Encounter the "Too many unapproved licenses:" message
+while running the "license-verify-profile" profile in "{{mvn deploy
+site...}}" step. This is caused by extra artifacts in the build tree that
+the license verification plugin does not recognized. Examples of these
+artifacts are:
+</tr>
+1. Eclipse control files, .classpath, .project
+1. User created log files ||
+<tr><th> Solution </td><td> Avoid the followings:
+</tr>
+1. Don't use Eclipse's svn plugin to "Check out" files to a Eclipse project.
+Simply use the svn command, as described in the release instructions.
+1. Don't create, directly or indirectly, any files under the release build
+tree.
+1. Don't use the IBM JDK. By default, the IBM JDK will create heap dumps
+when hitting the OOM condition in some of our tests. These extra files
+throw off the rat:check processing. If you must use the IBM JDK, then also
+set MAVEN_OPTS=-Xdump:none.
+ ||
+</table>
+
+<a name="ReleasingOpenJPA1.2.x(OldSCPSteps)-Resources"></a>
+## Resources
+
+* Apache Apache [Release FAQ](http://www.apache.org/dev/release.html)
+* [Signing Releases](http://apache.org/dev/release-signing.html)
+* [Wendy's notes on Release Signing](http://wiki.wsmoak.net/cgi-bin/wiki.pl?ReleaseSigning)
+* Apache [Mirroring Guidelines](http://apache.org/dev/mirrors.html)
+* Struts [Release Instructions](http://cwiki.apache.org/WW/creating-and-signing-a-distribution.html)
+ (upon which these instructions are based)
+ </div>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <div class="bottom_red_bar"></div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="black_box">
+ <div class="footer">
+ <div class="footer_l">
+ <div class="footer_r">
+ <div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="design_attribution">
+ Copyright (C) 2006,2012 The Apache Software Foundation. Licensed under <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License 2.0</a>.<br />
+ Apache, the Apache feather logo and OpenJPA are trademarks of The Apache Software Foundation.<br />
+ Other names may be trademarks of their respective owners.<br />
+ </div>
+
+ <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
+ </script>
+ <script type="text/javascript">
+ _uacct = "UA-1940143-1";
+ urchinTracker();
+ </script>
+
+ </body>
+</html>