openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mik...@apache.org
Subject svn commit: r1409057 [21/25] - in /openjpa/site: branches/ trunk/ trunk/cgi-bin/ trunk/content/ trunk/content/images/ trunk/lib/ trunk/resources/ trunk/templates/
Date Wed, 14 Nov 2012 01:50:14 GMT
Added: openjpa/site/trunk/content/publishing-serp-to-maven-central-repository.mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/publishing-serp-to-maven-central-repository.mdtext?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/publishing-serp-to-maven-central-repository.mdtext (added)
+++ openjpa/site/trunk/content/publishing-serp-to-maven-central-repository.mdtext Wed Nov 14 01:49:37 2012
@@ -0,0 +1,118 @@
+Title: Publishing Serp to Maven Central Repository
+<a name="PublishingSerptoMavenCentralRepository-PublishingSerptoMavenCentralRepository"></a>
+# Publishing Serp to Maven Central Repository
+<a name="PublishingSerptoMavenCentralRepository-SerpProject"></a>
+## Serp Project
+Serp is used by OpenJPA for the bytecode enhancement processing.  It is
+maintained as a [SourceForge project](http://sourceforge.net/projects/serp)
+.  Serp has been a very solid third-party dependent software project. 
+OpenJPA has had a dependency on Serp v1.13.1 for a long time.  Recently, a
+problem was discovered ([JIRA
+OPENJPA-2240|http://issues.apache.org/jira/browse/OPENJPA-2240]) which
+required an update to Serp.  Eventually, it was determined that this
+problem was resolved in the 1.14.1 version of Serp.  Unfortunately, the
+last version of Serp that was published to Maven Central was version
+1.13.1.  This page discusses how to get an updated Serp release into the
+Maven Central repository.
+
+SourceForge Serp:  https://sourceforge.net/projects/serp/
+Serp homepage:	http://serp.sourceforge.net
+Serp sourcecode:  http://serp.cvs.sourceforge.net/serp
+
+
+<a name="PublishingSerptoMavenCentralRepository-MavenInstructions"></a>
+## Maven Instructions
+The easiest way to get the updated artifacts for Serp 1.14.1 into Maven
+Central was to follow the instructions on this page: 
+https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository.
+ You will need a GPG utility and signature (instructions on that page). 
+You will also need a login for Sonatype's Nexus server (instructions also
+on that page).
+
+Since this exercise shouldn't be a common occurrence, I just went the
+manual route and signed each of the artifacts that were built into my local
+repository:
+
+    > gpg -ab serp-1.14.1-javadoc.jar
+    > gpg -ab serp-1.14.1.jar
+    > gpg -ab serp-1.14.1-sources.jar
+    > gpg -ab serp-1.14.1.pom
+
+
+And, then I created a bundle:
+
+    > jar -cvf serp-1.14.1-bundle.jar serp-*
+
+
+The bundle contained:
+
+    Archive:  serp-1.14.1-bundle.jar
+      Length     Date   Time    Name
+     --------    ----   ----    ----
+    	0  09-04-12 15:23   META-INF/
+           62  09-04-12 15:23   META-INF/MANIFEST.MF
+       962397  09-04-12 15:21   serp-1.14.1-javadoc.jar
+          499  09-04-12 15:22   serp-1.14.1-javadoc.jar.asc
+       140576  09-04-12 15:21   serp-1.14.1-sources.jar
+          499  09-04-12 15:21   serp-1.14.1-sources.jar.asc
+       206638  09-04-12 15:21   serp-1.14.1.jar
+          499  09-04-12 15:22   serp-1.14.1.jar.asc
+         5508  09-04-12 15:21   serp-1.14.1.pom
+          499  09-04-12 15:23   serp-1.14.1.pom.asc
+     --------		    -------
+      1317177		    10 files
+
+
+This bundle is what I uploaded to the Sonatype Staging repository as
+outlined on that [wiki page](https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository)
+.
+
+{note:title="Not documented.."}
+One process point that was not documented on that [wiki page](https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository)
+ was the need for a JIRA to be created against the OSSRH project (Open
+Source Project Repository Hosting).  This JIRA should include the Central
+Repository staging URL that is provided after you upload the bundle. 
+Here's an [example JIRA|https://issues.sonatype.org/browse/OSSRH-4247]
+ that worked for me.  If all else fails, contact Joel Orlina,
+jorlina@sonatype.com.
+{note}
+
+<a name="PublishingSerptoMavenCentralRepository-SerpCodeUpdates"></a>
+## Serp Code Updates
+In order to create the -javadoc and -sources jar files, I had to make a
+couple of minor updates to the existing pom file for serp 1.14.1.  I
+committed these changes to HEAD (1.14.2 snapshot) for future reference:
+
+          <plugin>
+    	  <artifactId>maven-source-plugin</artifactId>
+    	  <executions>
+    	    <execution>
+    		<id>attach-sources</id>
+    		<goals>
+    		    <goal>jar</goal>
+    		</goals>
+    	    </execution>
+    	 </executions>
+          </plugin>
+          <plugin>
+    	  <artifactId>maven-javadoc-plugin</artifactId>
+    	  <executions>
+    	    <execution>
+    		<id>attach-javadoc</id>
+    		<goals>
+    		    <goal>jar</goal>
+    		</goals>
+    	    </execution>
+    	 </executions>
+          </plugin>
+
+
+If we continue to require changes to Serp, we may want to do more extensive
+changes in the maven processing to make it easier to deploy the artifacts. 
+Several of the deployment locations in the pom.xml no longer exist.  I made
+a couple of updates, but the permissions don't show up right, so the
+deployment step is still manual.
+
+Another idea would be to consume Serp into OpenJPA as an Apache
+sub-project...	That might be the best long-term solution.  But, I will
+leave that for another day.

Added: openjpa/site/trunk/content/query-notes
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/query-notes?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/query-notes (added)
+++ openjpa/site/trunk/content/query-notes Wed Nov 14 01:49:37 2012
@@ -0,0 +1,18 @@
+name conflict: QueryImpl from JDBC vs. QueryImpl from kernel
+openjpa.kernel.jpql.JPQLParser
+joins are done by SelectImpl
+subselects have some issues especially with non-relationship 
+src/main/jjtree/org/apache/openjpa/kernel/jpql/JPQL.jjt has rules
+all queries always have a "candidate class" 
+openjpa.jdbc.kernel.exps.JDBCExpressionFactory implements openjpa.kernel.exps.ExpressionFactory
+openjpa.kernel.exps.InMemoryExpressionFactory implements openjpa.kernel.exps.ExpressionFactory
+can do in memory filtering by downcasting the JPA Query instance and passing it a collection to filter
+can traverse entity parameters via :param.firstname or :param.relationship.deptname
+DBDictionary contains fields that can be customized per database type
+JPQLExpressionBuilder does semantic analysis by walking the syntax tree and generating the semantic tree
+SQLFactoryImpl constructs the SQL for the query
+SQLBuffer is the result of applying DBDictionary rules to the semantic tree
+Can append SQLBuffer to another SQLBuffer for e.g. subselects
+SQLBuffer is almost a StringBuffer
+ResultSetResult will call ResultSet.getInt etc.
+

Added: openjpa/site/trunk/content/query-notes.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/query-notes.cwiki?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/query-notes.cwiki (added)
+++ openjpa/site/trunk/content/query-notes.cwiki Wed Nov 14 01:49:37 2012
@@ -0,0 +1,18 @@
+name conflict: QueryImpl from JDBC vs. QueryImpl from kernel
+openjpa.kernel.jpql.JPQLParser
+joins are done by SelectImpl
+subselects have some issues especially with non-relationship 
+src/main/jjtree/org/apache/openjpa/kernel/jpql/JPQL.jjt has rules
+all queries always have a "candidate class" 
+openjpa.jdbc.kernel.exps.JDBCExpressionFactory implements openjpa.kernel.exps.ExpressionFactory
+openjpa.kernel.exps.InMemoryExpressionFactory implements openjpa.kernel.exps.ExpressionFactory
+can do in memory filtering by downcasting the JPA Query instance and passing it a collection to filter
+can traverse entity parameters via :param.firstname or :param.relationship.deptname
+DBDictionary contains fields that can be customized per database type
+JPQLExpressionBuilder does semantic analysis by walking the syntax tree and generating the semantic tree
+SQLFactoryImpl constructs the SQL for the query
+SQLBuffer is the result of applying DBDictionary rules to the semantic tree
+Can append SQLBuffer to another SQLBuffer for e.g. subselects
+SQLBuffer is almost a StringBuffer
+ResultSetResult will call ResultSet.getInt etc.
+

Propchange: openjpa/site/trunk/content/query-notes.cwiki
------------------------------------------------------------------------------
    svn:eol-style = native

Added: openjpa/site/trunk/content/query-notes.mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/query-notes.mdtext?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/query-notes.mdtext (added)
+++ openjpa/site/trunk/content/query-notes.mdtext Wed Nov 14 01:49:37 2012
@@ -0,0 +1,24 @@
+Title: Query Notes
+name conflict: QueryImpl from JDBC vs. QueryImpl from kernel
+openjpa.kernel.jpql.JPQLParser
+joins are done by SelectImpl
+subselects have some issues especially with non-relationship 
+src/main/jjtree/org/apache/openjpa/kernel/jpql/JPQL.jjt has rules
+all queries always have a "candidate class" 
+openjpa.jdbc.kernel.exps.JDBCExpressionFactory implements
+openjpa.kernel.exps.ExpressionFactory
+openjpa.kernel.exps.InMemoryExpressionFactory implements
+openjpa.kernel.exps.ExpressionFactory
+can do in memory filtering by downcasting the JPA Query instance and
+passing it a collection to filter
+can traverse entity parameters via :param.firstname or
+:param.relationship.deptname
+DBDictionary contains fields that can be customized per database type
+JPQLExpressionBuilder does semantic analysis by walking the syntax tree and
+generating the semantic tree
+SQLFactoryImpl constructs the SQL for the query
+SQLBuffer is the result of applying DBDictionary rules to the semantic tree
+Can append SQLBuffer to another SQLBuffer for e.g. subselects
+SQLBuffer is almost a StringBuffer
+ResultSetResult will call ResultSet.getInt etc.
+

Added: openjpa/site/trunk/content/quick-start
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/quick-start?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/quick-start (added)
+++ openjpa/site/trunk/content/quick-start Wed Nov 14 01:49:37 2012
@@ -0,0 +1,40 @@
+{excerpt:hidden=true}Getting Started with OpenJPA{excerpt}
+
+h1. Quick Start Guide
+
+We know it can be hard to find the right help sometimes and search engines can be overwhelming, so we will try to put the most commonly asked for topics with some overview and links to more in-depth resources here for you to checkout, before wasting your time searching through our [Documentation] and [Mailing Lists] for help.
+
+
+h2. Runtime Dependencies
+
+To use OpenJPA as a stand-alone Java component or with a lightweight non-Java EE framework, please refer to the following [Build and Runtime Dependencies] page for the supported levels of Java SE.
+
+To use OpenJPA in a Java EE application server, please refer to the following [Integration] page for the known platforms that either include OpenJPA or have been tested with OpenJPA.
+
+
+h2. JPA Examples
+
+OpenJPA provides some simple examples as part of the binary distribution on the [Downloads] page.  The following [Samples] page provides quick start instructions on how to build and run these samples, along with pointers to other JPA samples from the Apache Geronimo project.
+
+
+h2. Enhancing Entities
+
+The JPA spec requires some type of monitoring of Entity objects, but the spec does not define how to implement this monitoring. Some JPA providers auto-generate new subclasses or proxy objects that front the user's Entity objects at *runtime*, while others use byte-code weaving technologies to enhance the actual Entity class objects at *build time*.  OpenJPA supports both [enhancement|Entity Enhancement] methods, but strongly suggests only using the *build time* enhancement.  The following [Entity Enhancement] page includes more details on both enhancement types, along with examples on how to setup *build time* enhancement in ANT, Maven and Eclipse environments.
+
+
+h2. Tools
+
+OpenJPA provides several design-time and runtime tools, to perform such tasks as entity enhancement, schema mapping, generating metamodel classes and to help migrate from other JPA providers.  Please checkout the [Tools] page for more details.
+
+
+h2. FAQ
+
+Some common questions concerning the history, architecture and usage of OpenJPA can be found on the [FAQ] page.
+
+
+h2. Take the Red Pill
+
+If you want to dive into the rabbit-hole (Hey, It's open source!), then checkout the [Found a Bug] page, which covers everything from posting questions to our mailing lists, to getting the source code and building it, and creating bug patches....
+
+\\
+

Added: openjpa/site/trunk/content/quick-start.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/quick-start.cwiki?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/quick-start.cwiki (added)
+++ openjpa/site/trunk/content/quick-start.cwiki Wed Nov 14 01:49:37 2012
@@ -0,0 +1,40 @@
+{excerpt:hidden=true}Getting Started with OpenJPA{excerpt}
+
+h1. Quick Start Guide
+
+We know it can be hard to find the right help sometimes and search engines can be overwhelming, so we will try to put the most commonly asked for topics with some overview and links to more in-depth resources here for you to checkout, before wasting your time searching through our [Documentation] and [Mailing Lists] for help.
+
+
+h2. Runtime Dependencies
+
+To use OpenJPA as a stand-alone Java component or with a lightweight non-Java EE framework, please refer to the following [Build and Runtime Dependencies] page for the supported levels of Java SE.
+
+To use OpenJPA in a Java EE application server, please refer to the following [Integration] page for the known platforms that either include OpenJPA or have been tested with OpenJPA.
+
+
+h2. JPA Examples
+
+OpenJPA provides some simple examples as part of the binary distribution on the [Downloads] page.  The following [Samples] page provides quick start instructions on how to build and run these samples, along with pointers to other JPA samples from the Apache Geronimo project.
+
+
+h2. Enhancing Entities
+
+The JPA spec requires some type of monitoring of Entity objects, but the spec does not define how to implement this monitoring. Some JPA providers auto-generate new subclasses or proxy objects that front the user's Entity objects at *runtime*, while others use byte-code weaving technologies to enhance the actual Entity class objects at *build time*.  OpenJPA supports both [enhancement|Entity Enhancement] methods, but strongly suggests only using the *build time* enhancement.  The following [Entity Enhancement] page includes more details on both enhancement types, along with examples on how to setup *build time* enhancement in ANT, Maven and Eclipse environments.
+
+
+h2. Tools
+
+OpenJPA provides several design-time and runtime tools, to perform such tasks as entity enhancement, schema mapping, generating metamodel classes and to help migrate from other JPA providers.  Please checkout the [Tools] page for more details.
+
+
+h2. FAQ
+
+Some common questions concerning the history, architecture and usage of OpenJPA can be found on the [FAQ] page.
+
+
+h2. Take the Red Pill
+
+If you want to dive into the rabbit-hole (Hey, It's open source!), then checkout the [Found a Bug] page, which covers everything from posting questions to our mailing lists, to getting the source code and building it, and creating bug patches....
+
+\\
+

Propchange: openjpa/site/trunk/content/quick-start.cwiki
------------------------------------------------------------------------------
    svn:eol-style = native

Added: openjpa/site/trunk/content/quick-start.mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/quick-start.mdtext?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/quick-start.mdtext (added)
+++ openjpa/site/trunk/content/quick-start.mdtext Wed Nov 14 01:49:37 2012
@@ -0,0 +1,82 @@
+Title: Quick Start
+{excerpt:hidden=true}Getting Started with OpenJPA{excerpt}
+
+<a name="QuickStart-QuickStartGuide"></a>
+# Quick Start Guide
+
+We know it can be hard to find the right help sometimes and search engines
+can be overwhelming, so we will try to put the most commonly asked for
+topics with some overview and links to more in-depth resources here for you
+to checkout, before wasting your time searching through our [Documentation](documentation.html)
+ and [Mailing Lists]
+ for help.
+
+
+<a name="QuickStart-RuntimeDependencies"></a>
+## Runtime Dependencies
+
+To use OpenJPA as a stand-alone Java component or with a lightweight
+non-Java EE framework, please refer to the following [Build and Runtime Dependencies](build-and-runtime-dependencies.html)
+ page for the supported levels of Java SE.
+
+To use OpenJPA in a Java EE application server, please refer to the
+following [Integration](integration.html)
+ page for the known platforms that either include OpenJPA or have been
+tested with OpenJPA.
+
+
+<a name="QuickStart-JPAExamples"></a>
+## JPA Examples
+
+OpenJPA provides some simple examples as part of the binary distribution on
+the [Downloads](downloads.html)
+ page.	The following [Samples]
+ page provides quick start instructions on how to build and run these
+samples, along with pointers to other JPA samples from the Apache Geronimo
+project.
+
+
+<a name="QuickStart-EnhancingEntities"></a>
+## Enhancing Entities
+
+The JPA spec requires some type of monitoring of Entity objects, but the
+spec does not define how to implement this monitoring. Some JPA providers
+auto-generate new subclasses or proxy objects that front the user's Entity
+objects at *runtime*, while others use byte-code weaving technologies to
+enhance the actual Entity class objects at *build time*.  OpenJPA supports
+both [enhancement](entity-enhancement.html)
+ methods, but strongly suggests only using the *build time* enhancement. 
+The following [Entity Enhancement]
+ page includes more details on both enhancement types, along with examples
+on how to setup *build time* enhancement in ANT, Maven and Eclipse
+environments.
+
+
+<a name="QuickStart-Tools"></a>
+## Tools
+
+OpenJPA provides several design-time and runtime tools, to perform such
+tasks as entity enhancement, schema mapping, generating metamodel classes
+and to help migrate from other JPA providers.  Please checkout the [Tools](tools.html)
+ page for more details.
+
+
+<a name="QuickStart-FAQ"></a>
+## FAQ
+
+Some common questions concerning the history, architecture and usage of
+OpenJPA can be found on the [FAQ](faq.html)
+ page.
+
+
+<a name="QuickStart-TaketheRedPill"></a>
+## Take the Red Pill
+
+If you want to dive into the rabbit-hole (Hey, It's open source!), then
+checkout the [Found a Bug](found-a-bug.html)
+ page, which covers everything from posting questions to our mailing lists,
+to getting the source code and building it, and creating bug patches....
+
+  
+  
+

Added: openjpa/site/trunk/content/recovering-from-a-vetoed-release
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/recovering-from-a-vetoed-release?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/recovering-from-a-vetoed-release (added)
+++ openjpa/site/trunk/content/recovering-from-a-vetoed-release Wed Nov 14 01:49:37 2012
@@ -0,0 +1,15 @@
+h2. Recovering from a bad release or a vetoed release
+
+Recovering from a bad release actually isn't that difficult. You'll have to delete the bad tag in SVN and rollback the version numbers in all of our pom.xml files. 
+
+h3. Delete the tag in svn
+{code:none}
+$ svn del https://svn.apache.org/repos/asf/openjpa/tags/1.2.0 -m "Rollback release"
+{code}
+h3. Rollback version numbers
+If you have perl installed you can do this in a single command for example to rollback from 1.2.1-SNAPSHOT to 1.2.0-SNAPSHOT
+{code:none}
+$ perl -pi -e "s;<version>1.2.1-SNAPSHOT</version>;<version>1.2.0-SNAPSHOT</version>;g" pom.xml */pom.xml */*/pom.xml
+{code}
+
+If you do not have perl installed you can use a similar tool to edit multiple files or edit them all by hand.

Added: openjpa/site/trunk/content/recovering-from-a-vetoed-release.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/recovering-from-a-vetoed-release.cwiki?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/recovering-from-a-vetoed-release.cwiki (added)
+++ openjpa/site/trunk/content/recovering-from-a-vetoed-release.cwiki Wed Nov 14 01:49:37 2012
@@ -0,0 +1,15 @@
+h2. Recovering from a bad release or a vetoed release
+
+Recovering from a bad release actually isn't that difficult. You'll have to delete the bad tag in SVN and rollback the version numbers in all of our pom.xml files. 
+
+h3. Delete the tag in svn
+{code:none}
+$ svn del https://svn.apache.org/repos/asf/openjpa/tags/1.2.0 -m "Rollback release"
+{code}
+h3. Rollback version numbers
+If you have perl installed you can do this in a single command for example to rollback from 1.2.1-SNAPSHOT to 1.2.0-SNAPSHOT
+{code:none}
+$ perl -pi -e "s;<version>1.2.1-SNAPSHOT</version>;<version>1.2.0-SNAPSHOT</version>;g" pom.xml */pom.xml */*/pom.xml
+{code}
+
+If you do not have perl installed you can use a similar tool to edit multiple files or edit them all by hand.

Propchange: openjpa/site/trunk/content/recovering-from-a-vetoed-release.cwiki
------------------------------------------------------------------------------
    svn:eol-style = native

Added: openjpa/site/trunk/content/recovering-from-a-vetoed-release.mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/recovering-from-a-vetoed-release.mdtext?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/recovering-from-a-vetoed-release.mdtext (added)
+++ openjpa/site/trunk/content/recovering-from-a-vetoed-release.mdtext Wed Nov 14 01:49:37 2012
@@ -0,0 +1,25 @@
+Title: Recovering from a vetoed release
+<a name="Recoveringfromavetoedrelease-Recoveringfromabadreleaseoravetoedrelease"></a>
+## Recovering from a bad release or a vetoed release
+
+Recovering from a bad release actually isn't that difficult. You'll have to
+delete the bad tag in SVN and rollback the version numbers in all of our
+pom.xml files. 
+
+<a name="Recoveringfromavetoedrelease-Deletethetaginsvn"></a>
+### Delete the tag in svn
+{code:none}
+$ svn del https://svn.apache.org/repos/asf/openjpa/tags/1.2.0 -m "Rollback
+release"
+
+    h3. Rollback version numbers
+    If you have perl installed you can do this in a single command for example
+to rollback from 1.2.1-SNAPSHOT to 1.2.0-SNAPSHOT
+    {code:none}
+    $ perl -pi -e
+"s;<version>1.2.1-SNAPSHOT</version>;<version>1.2.0-SNAPSHOT</version>;g"
+pom.xml */pom.xml */*/pom.xml
+
+
+If you do not have perl installed you can use a similar tool to edit
+multiple files or edit them all by hand.

Added: openjpa/site/trunk/content/related-projects
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/related-projects?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/related-projects (added)
+++ openjpa/site/trunk/content/related-projects Wed Nov 14 01:49:37 2012
@@ -0,0 +1,6 @@
+{excerpt:hidden=true}Projects related to OpenJPA{excerpt}
+
+ * [JDO|http://db.apache.org/jdo/]
+
+
+{note}TODO: More Links{note}
\ No newline at end of file

Added: openjpa/site/trunk/content/related-projects.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/related-projects.cwiki?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/related-projects.cwiki (added)
+++ openjpa/site/trunk/content/related-projects.cwiki Wed Nov 14 01:49:37 2012
@@ -0,0 +1,6 @@
+{excerpt:hidden=true}Projects related to OpenJPA{excerpt}
+
+ * [JDO|http://db.apache.org/jdo/]
+
+
+{note}TODO: More Links{note}
\ No newline at end of file

Propchange: openjpa/site/trunk/content/related-projects.cwiki
------------------------------------------------------------------------------
    svn:eol-style = native

Added: openjpa/site/trunk/content/related-projects.mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/related-projects.mdtext?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/related-projects.mdtext (added)
+++ openjpa/site/trunk/content/related-projects.mdtext Wed Nov 14 01:49:37 2012
@@ -0,0 +1,7 @@
+Title: Related Projects
+{excerpt:hidden=true}Projects related to OpenJPA{excerpt}
+
+ * [JDO](http://db.apache.org/jdo/)
+
+
+{note}TODO: More Links{note}

Added: openjpa/site/trunk/content/release-management
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/release-management?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/release-management (added)
+++ openjpa/site/trunk/content/release-management Wed Nov 14 01:49:37 2012
@@ -0,0 +1,40 @@
+h1. Release Management
+{children:depth=3}
+
+h2. Where should I put my fix? 
+Fixes should be targeted and committed on trunk first. Any other open releases are fair game, but may require approval from a release manager. 
+
+h2. Regarding Release Managers
+Once a formal release of OpenJPA has been approved, a release manager is assigned. The release manager is often (but not always) the same developer who performed the release. This release manager role is intended to be a long term branch maintainer who looks after the stability of a formal release. 
+
+The release manager(s) is(are) responsible for targeting fixes into a given version of OpenJPA.
+* Release managers may indicate this by targeting a JIRA issue for their branch or may issue a blanket statement that any fix will be accepted. 
+* In general only the release manager(s) should target a JIRA issue for a branch which they support. 
+** An exception to this rule is if the RM has committed changes for their branch and forgot to update the JIRA issue. 
+* Fixes should not be committed without RM approval. These changes may be reverted by the release manager. 
+
+h3. Some general guidelines for release managers
+* Fixes which are committed to an earlier release should also be present "up-stream". Ie a fix for 1.0.x should also appear in 1.2.x. 
+* Issues may not apply to every release, so the previous guideline may not always apply.
+
+h2. Release Managers for active branches.
+The current release managers for the active branches of OpenJPA are :
+|| branch || internal release number || release manager(s)|| Contact Release Manager before committing ||
+| 0.9.7-r547073 | | Srinivasa Segu | Yes |
+| 1.0.x | 1.0.5-SNAPSHOT | Heath Thomann, Donald Woods | Yes |
+| 1.1.x | 1.1.1-SNAPSHOT | Patrick Linskey, Abe White | Yes |
+| 1.2.x | 1.2.3-SNAPSHOT | Heath Thomann, Donald Woods |  Yes | 
+| 1.3.x | 1.3.0-SNAPSHOT | N/A* | No |
+| 2.0.x | 2.0.2-SNAPSHOT | Donald Woods, Heath Thomann | Yes |
+| 2.1.x | 2.1.1-SNAPSHOT | Heath Thomann | Yes |
+| 2.2.x | 2.2.1-SNAPSHOT | Albert Lee | Yes |
+| trunk | 2.3.0-SNAPSHOT | N/A*| No |
+\* There are no formal releases for these branches.
+
+
+h2. Continuous Builds
+
+We are using the Apache Hudson server for continuous builds of several releases.  Please checkout the [Automated Builds] page for more details.
+
+
+

Added: openjpa/site/trunk/content/release-management.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/release-management.cwiki?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/release-management.cwiki (added)
+++ openjpa/site/trunk/content/release-management.cwiki Wed Nov 14 01:49:37 2012
@@ -0,0 +1,40 @@
+h1. Release Management
+{children:depth=3}
+
+h2. Where should I put my fix? 
+Fixes should be targeted and committed on trunk first. Any other open releases are fair game, but may require approval from a release manager. 
+
+h2. Regarding Release Managers
+Once a formal release of OpenJPA has been approved, a release manager is assigned. The release manager is often (but not always) the same developer who performed the release. This release manager role is intended to be a long term branch maintainer who looks after the stability of a formal release. 
+
+The release manager(s) is(are) responsible for targeting fixes into a given version of OpenJPA.
+* Release managers may indicate this by targeting a JIRA issue for their branch or may issue a blanket statement that any fix will be accepted. 
+* In general only the release manager(s) should target a JIRA issue for a branch which they support. 
+** An exception to this rule is if the RM has committed changes for their branch and forgot to update the JIRA issue. 
+* Fixes should not be committed without RM approval. These changes may be reverted by the release manager. 
+
+h3. Some general guidelines for release managers
+* Fixes which are committed to an earlier release should also be present "up-stream". Ie a fix for 1.0.x should also appear in 1.2.x. 
+* Issues may not apply to every release, so the previous guideline may not always apply.
+
+h2. Release Managers for active branches.
+The current release managers for the active branches of OpenJPA are :
+|| branch || internal release number || release manager(s)|| Contact Release Manager before committing ||
+| 0.9.7-r547073 | | Srinivasa Segu | Yes |
+| 1.0.x | 1.0.5-SNAPSHOT | Heath Thomann, Donald Woods | Yes |
+| 1.1.x | 1.1.1-SNAPSHOT | Patrick Linskey, Abe White | Yes |
+| 1.2.x | 1.2.3-SNAPSHOT | Heath Thomann, Donald Woods |  Yes | 
+| 1.3.x | 1.3.0-SNAPSHOT | N/A* | No |
+| 2.0.x | 2.0.2-SNAPSHOT | Donald Woods, Heath Thomann | Yes |
+| 2.1.x | 2.1.1-SNAPSHOT | Heath Thomann | Yes |
+| 2.2.x | 2.2.1-SNAPSHOT | Albert Lee | Yes |
+| trunk | 2.3.0-SNAPSHOT | N/A*| No |
+\* There are no formal releases for these branches.
+
+
+h2. Continuous Builds
+
+We are using the Apache Hudson server for continuous builds of several releases.  Please checkout the [Automated Builds] page for more details.
+
+
+

Propchange: openjpa/site/trunk/content/release-management.cwiki
------------------------------------------------------------------------------
    svn:eol-style = native

Added: openjpa/site/trunk/content/release-management.mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/release-management.mdtext?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/release-management.mdtext (added)
+++ openjpa/site/trunk/content/release-management.mdtext Wed Nov 14 01:49:37 2012
@@ -0,0 +1,64 @@
+Title: Release Management
+<a name="ReleaseManagement-ReleaseManagement"></a>
+# Release Management
+{children:depth=3}
+
+<a name="ReleaseManagement-WhereshouldIputmyfix?"></a>
+## Where should I put my fix? 
+Fixes should be targeted and committed on trunk first. Any other open
+releases are fair game, but may require approval from a release manager. 
+
+<a name="ReleaseManagement-RegardingReleaseManagers"></a>
+## Regarding Release Managers
+Once a formal release of OpenJPA has been approved, a release manager is
+assigned. The release manager is often (but not always) the same developer
+who performed the release. This release manager role is intended to be a
+long term branch maintainer who looks after the stability of a formal
+release. 
+
+The release manager(s) is(are) responsible for targeting fixes into a given
+version of OpenJPA.
+* Release managers may indicate this by targeting a JIRA issue for their
+branch or may issue a blanket statement that any fix will be accepted. 
+* In general only the release manager(s) should target a JIRA issue for a
+branch which they support. 
+** An exception to this rule is if the RM has committed changes for their
+branch and forgot to update the JIRA issue. 
+* Fixes should not be committed without RM approval. These changes may be
+reverted by the release manager. 
+
+<a name="ReleaseManagement-Somegeneralguidelinesforreleasemanagers"></a>
+### Some general guidelines for release managers
+* Fixes which are committed to an earlier release should also be present
+"up-stream". Ie a fix for 1.0.x should also appear in 1.2.x. 
+* Issues may not apply to every release, so the previous guideline may not
+always apply.
+
+<a name="ReleaseManagement-ReleaseManagersforactivebranches."></a>
+## Release Managers for active branches.
+The current release managers for the active branches of OpenJPA are :
+<table>
+<tr><th> branch </th><th> internal release number </th><th> release manager(s)</th><th> Contact
+Release Manager before committing </th></tr>
+<tr><td> 0.9.7-r547073 </td><td> </td><td> Srinivasa Segu </td><td> Yes </td></tr>
+<tr><td> 1.0.x </td><td> 1.0.5-SNAPSHOT </td><td> Heath Thomann, Donald Woods </td><td> Yes </td></tr>
+<tr><td> 1.1.x </td><td> 1.1.1-SNAPSHOT </td><td> Patrick Linskey, Abe White </td><td> Yes </td></tr>
+<tr><td> 1.2.x </td><td> 1.2.3-SNAPSHOT </td><td> Heath Thomann, Donald Woods </td><td>  Yes </td></tr>
+<tr><td> 1.3.x </td><td> 1.3.0-SNAPSHOT </td><td> N/A* </td><td> No </td></tr>
+<tr><td> 2.0.x </td><td> 2.0.2-SNAPSHOT </td><td> Donald Woods, Heath Thomann </td><td> Yes </td></tr>
+<tr><td> 2.1.x </td><td> 2.1.1-SNAPSHOT </td><td> Heath Thomann </td><td> Yes </td></tr>
+<tr><td> 2.2.x </td><td> 2.2.1-SNAPSHOT </td><td> Albert Lee </td><td> Yes </td></tr>
+<tr><td> trunk </td><td> 2.3.0-SNAPSHOT </td><td> N/A*</td><td> No </td></tr>
+\* There are no formal releases for these branches.
+</table>
+
+
+<a name="ReleaseManagement-ContinuousBuilds"></a>
+## Continuous Builds
+
+We are using the Apache Hudson server for continuous builds of several
+releases.  Please checkout the [Automated Builds](automated-builds.html)
+ page for more details.
+
+
+

Added: openjpa/site/trunk/content/release-setup
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/release-setup?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/release-setup (added)
+++ openjpa/site/trunk/content/release-setup Wed Nov 14 01:49:37 2012
@@ -0,0 +1,195 @@
+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}
+
+h3. Create and install a SSH key
+
+# Open a shell window.  If using Windows, open a cygwin window.
+# Use ssh-keygen to create an SSH key.
+{note}
+* ssh-keygen dsa key type only accept 1024 bits; use rsa / 4096 bits instead.{note}
+{code:none}
+$ ssh-keygen -t rsa -b 4096
+{code}
+Program defaults should be fine.  No passphrase is required for the ssh key generation.  The keys will be saved in ~/.ssh/id_rsa (private) and ~/.ssh/id_rsa.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}
+# {{scp}} your SSH public key ~/.ssh/id_rsa.pub created in last step to ~/id_rsa.pub on people.apache.org.
+{code:none} 
+$ cd ~/.ssh
+$ scp id_rsa.pub <your userid>@people.apache.org:id_rsa.pub 
+$ You will be prompted for your password.
+{code}
+# Use ssh to login to people.apache.org 
+{code:none}
+$ cd ~
+$ ssh <your userid>@people.apache.org
+{code}
+At this point, you will still be prompted for your password.
+# 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
+{code}
+# Move or append ~/id_rsa.pub to ~/.ssh/authorized_keys and change its file mode to 600.
+{code:none}
+$ mv ~/id_rsa.pub ~/.ssh/authorized_keys
+or
+$ cat ~/id_rsa.pub >> ~/.ssh/authorized_keys
+$ chmod 600 ~/.ssh/authorized_keys
+{code}
+{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}
+# Exit out of this ssh session.
+# 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
+{code} 
+{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}
+
+
+h3. Create a GPG key
+
+# Open a shell window.  If using Windows, open a cygwin window.
+{info}
+* The generated keys are stored in:
+** *nix - $HOME/.gnupg
+** Windows XP - %HOME%\Application Data\gnupg
+** Windows 7 - C:\ProgramData\GNU\etc\gnupg
+* "gpg --version" shows the GnuPG's home location.
+* Follow the latest steps and guides on the ASF website at [http://www.apache.org/dev/openpgp.html#generate-key] as you need to disable using SHA1 and new keys should be 4096 bits. Append the following text to gpg.conf.
+{code:none}
+personal-digest-preferences SHA512
+cert-digest-algo SHA512
+default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
+{code}
+** If you are using an existing gpg certificate, update your current certificate with the above preference using:
+{code:none}
+leealber@jpadev:~/.gnupg$ gpg --edit-key Albert Lee
+Secret key is available.
+
+pub  1024D/8007117F  created: 2007-11-05  expires: never       usage: SC  
+                     trust: ultimate      validity: ultimate
+sub  2048g/8D910F8A  created: 2007-11-05  expires: never       usage: E   
+[ultimate] (1). Albert Lee (CODE SIGNING KEY) <allee8285@apache.org>
+
+Invalid command  (try "help")
+
+Command> showpref
+[ultimate] (1). Albert Lee (CODE SIGNING KEY) <allee8285@apache.org>
+     Cipher: AES256, AES192, AES, CAST5, 3DES
+     Digest: SHA512, SHA384, SHA256, SHA224, SHA1
+     Compression: ZLIB, BZIP2, ZIP, Uncompressed
+     Features: MDC, Keyserver no-modify
+
+Command> setpref SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
+Set preference list to:
+     Cipher: AES256, AES192, AES, CAST5, 3DES
+     Digest: SHA512, SHA384, SHA256, SHA224, SHA1
+     Compression: ZLIB, BZIP2, ZIP, Uncompressed
+     Features: MDC, Keyserver no-modify
+Really update the preferences? (y/N) y
+
+pub  1024D/8007117F  created: 2007-11-05  expires: never       usage: SC  
+                     trust: ultimate      validity: ultimate
+sub  2048g/8D910F8A  created: 2007-11-05  expires: never       usage: E   
+[ultimate] (1). Albert Lee (CODE SIGNING KEY) <allee8285@apache.org>
+
+Command>{code}
+{info}
+# Generate a key-pair with gpg, using default key kind ("DSA and Elgamal") and ELG-E keys size (2048).
+{code:none}
+$ gpg --gen-key
+{code}
+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}
+* Save the content in this subdirectory to a safe media. This contains your private key used to sign all the release materials.
+{info}
+# Backup your cygwin home directory to another media
+# Append your public key to {{[https://svn.apache.org/repos/asf/openjpa/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 releases. 
+{code:none}
+$ ( gpg --list-sigs <Real Name> && gpg --armor --export <Real Name> ) >> KEYS
+{code}
+{info}
+* The {{[https://svn.apache.org/repos/asf/openjpa/KEYS]}} file is updated via normal svn commit procedures.
+{code}
+svn co https://svn.apache.org/repos/asf/openjpa --depth empty
+cd openjpa
+svn up KEYS
+( gpg --list-sigs <Real Name> && gpg --armor --export <Real Name> ) >> KEYS
+svn commit KEYS --message "update gpg public key for ME."
+{code}
+* The one under www.apache.org/dist/ has to be manually updated. 
+{code}
+scp KEYS yourid@people.apache.org:/www/www.apache.org/dist/openjpa/KEYS
+{code}
+{info}
+# Submit your public key to a key server. E.g. [http://pgp.surfnet.nl:11371/] or [http://pgp.mit.edu/]
+# Following the instructions in [http://people.apache.org/~henkp/trust/] and ask multiple (at least 3) current Apache committers to sign your public key.
+
+h3. Update Maven settings for our servers
+
+# Create a settings.xml under .m2
+| | {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>
+       <!-- SCP settings for people.apache.org -->
+       <server>
+          <id>people.apache.org</id>
+          <username>$USERNAME</username>
+          <privateKey>$PATH_TO_PRIVATE_KEY</privateKey>
+          <passphrase>$SSH_PASSPHRASE</passphrase>
+          <directoryPermissions>775</directoryPermissions>
+          <filePermissions>644</filePermissions>
+          <!-- following is only for Windows only
+          <configuration>
+              <sshExecutable>plink</sshExecutable>
+              <scpExecutable>pscp</scpExecutable>
+              <scpArgs>-2Bp</scpArgs>
+              <sshArgs>-2</sshArgs>
+          </configuration>
+          -->
+       </server>
+       <!-- ASF Nexus settings -->
+       <server>
+           <id>apache.snapshots.https</id>
+           <username>$USERNAME</username>
+           <password>$APACHE_LDAP_PWD</password>
+       </server>
+       <server>
+           <id>apache.releases.https</id>
+           <username>$USERNAME</username>
+           <password>$APACHE_LDAP_PWD</password>
+       </server>
+    </servers> 
+    <profiles>
+        <profile>
+            <id>apache-release</id>
+            <properties>
+                <site.deploy.user.name>$USERNAME</site.deploy.user.name>
+                <gpg.passphrase>$GPG_PASSPHRASE</gpg.passphrase>
+            </properties>
+        </profile>
+        <profile>
+            <id>gpg-passphrase</id>
+            <properties>
+                <gpg.passphrase>$GPG_PASSPHRASE</gpg.passphrase>
+            </properties>
+        </profile>
+    </profiles>
+</settings>
+{code}
+{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_rsa.  For Windows' cygwin users, you will need to enter the full cygwin path:  /cygdrive/c/cygwin/home/yourLocalUserId/.ssh/id_rsa.
+* {{$SSH_PASSPHRASE}} for the supplied {{$PATH_TO_PRIVATE_KEY}}.  If you don't use this in your settings.xml file, then you will be prompted for it during the Release processing.
+* {{$GPG_PASSPHRASE}} is pass phase for the GPG key.
+* {{$APACHE_LDAP_PWD}} is your Apache LDAP password, which is shared between SVN and password login for  people.apache.org.
+{info}

Added: openjpa/site/trunk/content/release-setup.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/release-setup.cwiki?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/release-setup.cwiki (added)
+++ openjpa/site/trunk/content/release-setup.cwiki Wed Nov 14 01:49:37 2012
@@ -0,0 +1,195 @@
+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}
+
+h3. Create and install a SSH key
+
+# Open a shell window.  If using Windows, open a cygwin window.
+# Use ssh-keygen to create an SSH key.
+{note}
+* ssh-keygen dsa key type only accept 1024 bits; use rsa / 4096 bits instead.{note}
+{code:none}
+$ ssh-keygen -t rsa -b 4096
+{code}
+Program defaults should be fine.  No passphrase is required for the ssh key generation.  The keys will be saved in ~/.ssh/id_rsa (private) and ~/.ssh/id_rsa.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}
+# {{scp}} your SSH public key ~/.ssh/id_rsa.pub created in last step to ~/id_rsa.pub on people.apache.org.
+{code:none} 
+$ cd ~/.ssh
+$ scp id_rsa.pub <your userid>@people.apache.org:id_rsa.pub 
+$ You will be prompted for your password.
+{code}
+# Use ssh to login to people.apache.org 
+{code:none}
+$ cd ~
+$ ssh <your userid>@people.apache.org
+{code}
+At this point, you will still be prompted for your password.
+# 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
+{code}
+# Move or append ~/id_rsa.pub to ~/.ssh/authorized_keys and change its file mode to 600.
+{code:none}
+$ mv ~/id_rsa.pub ~/.ssh/authorized_keys
+or
+$ cat ~/id_rsa.pub >> ~/.ssh/authorized_keys
+$ chmod 600 ~/.ssh/authorized_keys
+{code}
+{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}
+# Exit out of this ssh session.
+# 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
+{code} 
+{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}
+
+
+h3. Create a GPG key
+
+# Open a shell window.  If using Windows, open a cygwin window.
+{info}
+* The generated keys are stored in:
+** *nix - $HOME/.gnupg
+** Windows XP - %HOME%\Application Data\gnupg
+** Windows 7 - C:\ProgramData\GNU\etc\gnupg
+* "gpg --version" shows the GnuPG's home location.
+* Follow the latest steps and guides on the ASF website at [http://www.apache.org/dev/openpgp.html#generate-key] as you need to disable using SHA1 and new keys should be 4096 bits. Append the following text to gpg.conf.
+{code:none}
+personal-digest-preferences SHA512
+cert-digest-algo SHA512
+default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
+{code}
+** If you are using an existing gpg certificate, update your current certificate with the above preference using:
+{code:none}
+leealber@jpadev:~/.gnupg$ gpg --edit-key Albert Lee
+Secret key is available.
+
+pub  1024D/8007117F  created: 2007-11-05  expires: never       usage: SC  
+                     trust: ultimate      validity: ultimate
+sub  2048g/8D910F8A  created: 2007-11-05  expires: never       usage: E   
+[ultimate] (1). Albert Lee (CODE SIGNING KEY) <allee8285@apache.org>
+
+Invalid command  (try "help")
+
+Command> showpref
+[ultimate] (1). Albert Lee (CODE SIGNING KEY) <allee8285@apache.org>
+     Cipher: AES256, AES192, AES, CAST5, 3DES
+     Digest: SHA512, SHA384, SHA256, SHA224, SHA1
+     Compression: ZLIB, BZIP2, ZIP, Uncompressed
+     Features: MDC, Keyserver no-modify
+
+Command> setpref SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
+Set preference list to:
+     Cipher: AES256, AES192, AES, CAST5, 3DES
+     Digest: SHA512, SHA384, SHA256, SHA224, SHA1
+     Compression: ZLIB, BZIP2, ZIP, Uncompressed
+     Features: MDC, Keyserver no-modify
+Really update the preferences? (y/N) y
+
+pub  1024D/8007117F  created: 2007-11-05  expires: never       usage: SC  
+                     trust: ultimate      validity: ultimate
+sub  2048g/8D910F8A  created: 2007-11-05  expires: never       usage: E   
+[ultimate] (1). Albert Lee (CODE SIGNING KEY) <allee8285@apache.org>
+
+Command>{code}
+{info}
+# Generate a key-pair with gpg, using default key kind ("DSA and Elgamal") and ELG-E keys size (2048).
+{code:none}
+$ gpg --gen-key
+{code}
+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}
+* Save the content in this subdirectory to a safe media. This contains your private key used to sign all the release materials.
+{info}
+# Backup your cygwin home directory to another media
+# Append your public key to {{[https://svn.apache.org/repos/asf/openjpa/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 releases. 
+{code:none}
+$ ( gpg --list-sigs <Real Name> && gpg --armor --export <Real Name> ) >> KEYS
+{code}
+{info}
+* The {{[https://svn.apache.org/repos/asf/openjpa/KEYS]}} file is updated via normal svn commit procedures.
+{code}
+svn co https://svn.apache.org/repos/asf/openjpa --depth empty
+cd openjpa
+svn up KEYS
+( gpg --list-sigs <Real Name> && gpg --armor --export <Real Name> ) >> KEYS
+svn commit KEYS --message "update gpg public key for ME."
+{code}
+* The one under www.apache.org/dist/ has to be manually updated. 
+{code}
+scp KEYS yourid@people.apache.org:/www/www.apache.org/dist/openjpa/KEYS
+{code}
+{info}
+# Submit your public key to a key server. E.g. [http://pgp.surfnet.nl:11371/] or [http://pgp.mit.edu/]
+# Following the instructions in [http://people.apache.org/~henkp/trust/] and ask multiple (at least 3) current Apache committers to sign your public key.
+
+h3. Update Maven settings for our servers
+
+# Create a settings.xml under .m2
+| | {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>
+       <!-- SCP settings for people.apache.org -->
+       <server>
+          <id>people.apache.org</id>
+          <username>$USERNAME</username>
+          <privateKey>$PATH_TO_PRIVATE_KEY</privateKey>
+          <passphrase>$SSH_PASSPHRASE</passphrase>
+          <directoryPermissions>775</directoryPermissions>
+          <filePermissions>644</filePermissions>
+          <!-- following is only for Windows only
+          <configuration>
+              <sshExecutable>plink</sshExecutable>
+              <scpExecutable>pscp</scpExecutable>
+              <scpArgs>-2Bp</scpArgs>
+              <sshArgs>-2</sshArgs>
+          </configuration>
+          -->
+       </server>
+       <!-- ASF Nexus settings -->
+       <server>
+           <id>apache.snapshots.https</id>
+           <username>$USERNAME</username>
+           <password>$APACHE_LDAP_PWD</password>
+       </server>
+       <server>
+           <id>apache.releases.https</id>
+           <username>$USERNAME</username>
+           <password>$APACHE_LDAP_PWD</password>
+       </server>
+    </servers> 
+    <profiles>
+        <profile>
+            <id>apache-release</id>
+            <properties>
+                <site.deploy.user.name>$USERNAME</site.deploy.user.name>
+                <gpg.passphrase>$GPG_PASSPHRASE</gpg.passphrase>
+            </properties>
+        </profile>
+        <profile>
+            <id>gpg-passphrase</id>
+            <properties>
+                <gpg.passphrase>$GPG_PASSPHRASE</gpg.passphrase>
+            </properties>
+        </profile>
+    </profiles>
+</settings>
+{code}
+{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_rsa.  For Windows' cygwin users, you will need to enter the full cygwin path:  /cygdrive/c/cygwin/home/yourLocalUserId/.ssh/id_rsa.
+* {{$SSH_PASSPHRASE}} for the supplied {{$PATH_TO_PRIVATE_KEY}}.  If you don't use this in your settings.xml file, then you will be prompted for it during the Release processing.
+* {{$GPG_PASSPHRASE}} is pass phase for the GPG key.
+* {{$APACHE_LDAP_PWD}} is your Apache LDAP password, which is shared between SVN and password login for  people.apache.org.
+{info}

Propchange: openjpa/site/trunk/content/release-setup.cwiki
------------------------------------------------------------------------------
    svn:eol-style = native

Added: openjpa/site/trunk/content/release-setup.mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/release-setup.mdtext?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/release-setup.mdtext (added)
+++ openjpa/site/trunk/content/release-setup.mdtext Wed Nov 14 01:49:37 2012
@@ -0,0 +1,244 @@
+Title: Release 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="ReleaseSetup-CreateandinstallaSSHkey"></a>
+### Create and install a SSH key
+
+1. Open a shell window.	If using Windows, open a cygwin window.
+1. Use ssh-keygen to create an SSH key.
+{note}
+* ssh-keygen dsa key type only accept 1024 bits; use rsa / 4096 bits
+instead.{note}
+{code:none}
+$ ssh-keygen -t rsa -b 4096
+
+    Program defaults should be fine.  No passphrase is required for the ssh key
+generation.  The keys will be saved in ~/.ssh/id_rsa (private) and
+~/.ssh/id_rsa.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}
+    # {{scp}} your SSH public key ~/.ssh/id_rsa.pub created in last step to
+~/id_rsa.pub on people.apache.org.
+    {code:none} 
+    $ cd ~/.ssh
+    $ scp id_rsa.pub <your userid>@people.apache.org:id_rsa.pub 
+    $ You will be prompted for your password.
+
+1. Use ssh to login to people.apache.org 
+{code:none}
+$ cd ~
+$ ssh <your userid>@people.apache.org
+
+    At this point, you will still be prompted for your password.
+    # 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
+
+1. Move or append ~/id_rsa.pub to ~/.ssh/authorized_keys and change its file
+mode to 600.
+{code:none}
+$ mv ~/id_rsa.pub ~/.ssh/authorized_keys
+or
+$ cat ~/id_rsa.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}
+    # Exit out of this ssh session.
+    # 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}
+
+
+<a name="ReleaseSetup-CreateaGPGkey"></a>
+### Create a GPG key
+
+1. Open a shell window.	If using Windows, open a cygwin window.
+{info}
+* The generated keys are stored in:
+** *nix - $HOME/.gnupg
+** Windows XP - %HOME%\Application Data\gnupg
+** Windows 7 - C:\ProgramData\GNU\etc\gnupg
+* "gpg --version" shows the GnuPG's home location.
+* 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. Append
+the following text to gpg.conf.
+{code:none}
+personal-digest-preferences SHA512
+cert-digest-algo SHA512
+default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5
+ZLIB BZIP2 ZIP Uncompressed
+
+    ** If you are using an existing gpg certificate, update your current
+certificate with the above preference using:
+    {code:none}
+    leealber@jpadev:~/.gnupg$ gpg --edit-key Albert Lee
+    Secret key is available.
+    
+    pub  1024D/8007117F  created: 2007-11-05  expires: never       usage: SC  
+    		     trust: ultimate	  validity: ultimate
+    sub  2048g/8D910F8A  created: 2007-11-05  expires: never       usage: E   
+    [ultimate]
+ (1). Albert Lee (CODE SIGNING KEY) <allee8285@apache.org>
+    
+    Invalid command  (try "help")
+    
+    Command> showpref
+    [ultimate]
+ (1). Albert Lee (CODE SIGNING KEY) <allee8285@apache.org>
+         Cipher: AES256, AES192, AES, CAST5, 3DES
+         Digest: SHA512, SHA384, SHA256, SHA224, SHA1
+         Compression: ZLIB, BZIP2, ZIP, Uncompressed
+         Features: MDC, Keyserver no-modify
+    
+    Command> setpref SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB
+BZIP2 ZIP Uncompressed
+    Set preference list to:
+         Cipher: AES256, AES192, AES, CAST5, 3DES
+         Digest: SHA512, SHA384, SHA256, SHA224, SHA1
+         Compression: ZLIB, BZIP2, ZIP, Uncompressed
+         Features: MDC, Keyserver no-modify
+    Really update the preferences? (y/N) y
+    
+    pub  1024D/8007117F  created: 2007-11-05  expires: never       usage: SC  
+    		     trust: ultimate	  validity: ultimate
+    sub  2048g/8D910F8A  created: 2007-11-05  expires: never       usage: E   
+    [ultimate]
+ (1). Albert Lee (CODE SIGNING KEY) <allee8285@apache.org>
+    
+    Command>{code}
+    {info}
+    # Generate a key-pair with gpg, using default key kind ("DSA and Elgamal")
+and ELG-E keys size (2048).
+    {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}
+* Save the content in this subdirectory to a safe media. This contains your
+private key used to sign all the release materials.
+{info}
+1. Backup your cygwin home directory to another media
+1. Append your public key to {{[https://svn.apache.org/repos/asf/openjpa/KEYS](https://svn.apache.org/repos/asf/openjpa/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 releases. 
+{code:none}
+$ ( gpg --list-sigs <Real Name> && gpg --armor --export <Real Name> ) >>
+KEYS
+
+    {info}
+    * The {{[https://svn.apache.org/repos/asf/openjpa/KEYS]
+}} file is updated via normal svn commit procedures.
+
+svn co https://svn.apache.org/repos/asf/openjpa --depth empty
+cd openjpa
+svn up KEYS
+( gpg --list-sigs <Real Name> && gpg --armor --export <Real Name> ) >> KEYS
+svn commit KEYS --message "update gpg public key for ME."
+
+    * The one under www.apache.org/dist/ has to be manually updated. 
+
+scp KEYS yourid@people.apache.org:/www/www.apache.org/dist/openjpa/KEYS
+
+    {info}
+    # Submit your public key to a key server. E.g. [http://pgp.surfnet.nl:11371/]
+ or [http://pgp.mit.edu/]
+    # Following the instructions in [http://people.apache.org/~henkp/trust/]
+ and ask multiple (at least 3) current Apache committers to sign your
+public key.
+    
+    h3. Update Maven settings for our servers
+    
+    # Create a settings.xml under .m2
+    | | {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>
+           <!-- SCP settings for people.apache.org -->
+           <server>
+    	  <id>people.apache.org</id>
+    	  <username>$USERNAME</username>
+    	  <privateKey>$PATH_TO_PRIVATE_KEY</privateKey>
+    	  <passphrase>$SSH_PASSPHRASE</passphrase>
+    	  <directoryPermissions>775</directoryPermissions>
+    	  <filePermissions>644</filePermissions>
+    	  <!-- following is only for Windows only
+    	  <configuration>
+    	      <sshExecutable>plink</sshExecutable>
+    	      <scpExecutable>pscp</scpExecutable>
+    	      <scpArgs>-2Bp</scpArgs>
+    	      <sshArgs>-2</sshArgs>
+    	  </configuration>
+    	  -->
+           </server>
+           <!-- ASF Nexus settings -->
+           <server>
+    	   <id>apache.snapshots.https</id>
+    	   <username>$USERNAME</username>
+    	   <password>$APACHE_LDAP_PWD</password>
+           </server>
+           <server>
+    	   <id>apache.releases.https</id>
+    	   <username>$USERNAME</username>
+    	   <password>$APACHE_LDAP_PWD</password>
+           </server>
+        </servers> 
+        <profiles>
+    	<profile>
+    	    <id>apache-release</id>
+    	    <properties>
+    		<site.deploy.user.name>$USERNAME</site.deploy.user.name>
+    		<gpg.passphrase>$GPG_PASSPHRASE</gpg.passphrase>
+    	    </properties>
+    	</profile>
+    	<profile>
+    	    <id>gpg-passphrase</id>
+    	    <properties>
+    		<gpg.passphrase>$GPG_PASSPHRASE</gpg.passphrase>
+    	    </properties>
+    	</profile>
+        </profiles>
+    </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_rsa.  For Windows' cygwin users,
+you will need to enter the full cygwin path: 
+/cygdrive/c/cygwin/home/yourLocalUserId/.ssh/id_rsa.
+* *$SSH_PASSPHRASE* for the supplied *$PATH_TO_PRIVATE_KEY*.  If you
+don't use this in your settings.xml file, then you will be prompted for it
+during the Release processing.
+* *$GPG_PASSPHRASE* is pass phase for the GPG key.
+* *$APACHE_LDAP_PWD* is your Apache LDAP password, which is shared
+between SVN and password login for  people.apache.org.
+{info}

Added: openjpa/site/trunk/content/releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps)
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/releasing-openjpa-1.0.x-or-1.1.x-%28old-scp-steps%29?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps) (added)
+++ openjpa/site/trunk/content/releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps) Wed Nov 14 01:49:37 2012
@@ -0,0 +1,343 @@
+{excerpt:hidden=true}Instructions for creating an official OpenJPA release{excerpt}
+{scrollbar}
+
+h1. Making an OpenJPA 1.0.x or 1.1.x Release
+
+These instructions guide the release manager through the steps of making an official OpenJPA release.
+
+h2. Prerequisites
+
+# You should read the [OpenJPA Release Policy|OpenJPA Release Policy] to decide on the name of the new release, based on the content.
+# You should read the Apache [Release FAQ|http://www.apache.org/dev/release.html]
+# You must have shell access to people.apache.org
+# You must have the following utilities installed on your local machine and available in your path:
+#* [JDK 1.4 / 1.5|http://java.sun.com/]
+#* [ssh|http://www.openssh.com/]
+#* [Maven 2|http://maven.apache.org/]
+#* [gnupg|http://www.gnupg.org/]
+# For Windows users, install [Cygwin|http://cygwin.com/] in addition to the above utilities
+#* Make sure the Net/openssh and Utils/gnupg packages are installed that come with Cygwin installation. 
+#* Optional: [Putty|http://www.chiark.greenend.org.uk/~sgtatham/putty/]
+
+h2. Tasks that need to be performed for each release
+
+{info}In the examples below, it is assumed that the release name will be *1.0.1*, and that the current checked-in version name is *1.0.1-SNAPSHOT* and stored in the branch named *1.0.x*.{info}
+|| Monday, 12:00 | Make sure the [#One time setup] steps have been performed \\ ||
+|| Monday, 12:01 | 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}
+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
+{code} ||
+|| Monday, 12:02 | Check out a clean branch from which to build the release: \\
+{code:none}
+svn checkout https://svn.apache.org/repos/asf/openjpa/branches/1.0.1
+cd 1.0.1
+{code} \\
+{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 "[#Space Character in Build Root Path]"{note} ||
+|| Monday, 12:03 | Update all the POMs to remove "-SNAPSHOT" suffix from the version. If you have perl installed, you can easily do it with a single command: \\
+{code:none}
+perl -pi -e "s;<version>1.0.1-SNAPSHOT</version>;<version>1.0.1</version>;g" \
+    pom.xml */pom.xml */*/pom.xml
+{code}
+Update the {{<scm.dir>}} property in the top level pom.xml to the 1.0.1 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"
+{code} ||
+|| Monday, 12:21 | Perform an initial build and install it in the local repository (this step is only required because of an [open bug|http://jira.codehaus.org/browse/MJAVADOC-116] with Maven's javadoc plugin): \\
+{code:none}
+mvn clean install -Dtest=false
+{code} ||
+|| Monday, 12:23 | Now build the release locally, which will build and 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 *target/site/downloads/*, and sign the release files. \\
+{code:none}
+export MAVEN_OPTS=-Xmx1000m
+mvn --batch-mode deploy site \
+    -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
+{code}\\
+{note}This operation will also sign the release files with the *gpg* utility using the <username>@apache.org key. If your code signing key is under a different address, specify it by appending the following argument to the command above: \-Dopenjpa.release.keyAlias=mysigningalias@somedomain.org{note}\\
+{note}The *java14.jar* path should be changed to the local install path for the JDK 1.4 rt.jar so that JDK 1.4 verification can take place.{note}\\
+{note}The *tck.zip* path should be changed to the local install path to the JPA TCK so that the TCK can be run against the release. If you are not licensed to access the TCK, remove the {{tck-profile}} profile and {{-Dtck.zip}} property from the command. Ask someone who has access to run the TCK for you. {note}\\
+{note} The {{examples-profile}} has problem running automatically in this maven build task. You will need to run the examples manually. Run the maven command without the {{examples-profile}}, then perform the following steps to run the example:
+{code}
+mkdir openjpa-integration\examples\target\examples
+unzip target\site\downloads\apache-openjpa-1.0.1-binary.zip -d 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
+{code}
+{note} ||
+|| Monday, 13:00 | Verify the signatures: \\
+{code:none}
+gpg --multifile --verify target/site/downloads/*.asc
+{code} ||
+|| Monday, 13:01 | Upload the release candidate to [http://openjpa.apache.org/builds/1.0.1/downloads/]: \\
+{code:none}
+mvn site:deploy
+{code}{warning}
+Bear in mind that uploads to *people.apache.org/www/openjpa.apache.org/builds/* are not visible at [http://openjpa.apache.org/builds] until after the hourly synchronization has taken place, as described at [http://www.apache.org/dev/project-site.html].
+{warning}||
+|| Monday, 15:00 | Start a vote for the release on the [mailto:dev@openjpa.apache.org] 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|http://www.nabble.com/-VOTE--Approve-OpenJPA-1.0.0-release-%284th-attempt%29-p12305349.html] ||
+|| Tuesday, Wednesday | While waiting for the vote to complete, perform whatever manual review and testing on the release you deem appropriate. ||
+|| Thursday, 15:00 | If the vote is successful after 3 days tally the votes in an email to [mailto:dev@openjpa.apache.org], like [this one|http://www.nabble.com/-VOTE-RESULT--Approve-OpenJPA-1.0.0-release-%284th-attempt%29-p12379716.html]. \\ ||
+|| Thursday, 15:10 | Make the OpenJPA assemblies available to the Apache mirroring system by copying them over on *people.apache.org*:\\
+{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
+{code}{warning}
+The OpenJPA binary release will be available via the link [http://www.apache.org/dyn/closer.cgi/openjpa/1.0.1/apache-openjpa-1.0.1-binary.zip] 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
+{code} ||
+|| Thursday, 15:16 | Check out the parent branch and bump up the release number to be the next snapshot version: \\
+{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 */pom.xml */*/pom.xml
+svn commit -m "Updating version in branch to 1.0.2-SNAPSHOT"
+{code} ||
+|| Thursday, 15:20 | Update the [http://cwiki.apache.org/openjpa/downloads.html] page with links to the download mirrors, using the existing entries as templates. {note}All artifacts (*apache-openjpa-1.0.1-binary.zip* and *apache-openjpa-1.0.1-source.zip*) *must* link to the mirrors, but signatures (*apache-openjpa-1.0.1-binary.zip.asc* and *apache-openjpa-1.0.1-source.zip.asc*) *must not* link to mirrors.{note}||
+|| Thursday, 15:30 | The documentation on the server-side must manually be extracted on *people.apache.org*, 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
+{code} \\
+Then point the links on [http://openjpa.apache.org/documentation.html] to: \\
+ * HTML Manual: [http://openjpa.apache.org/builds/1.0.1/apache-openjpa-1.0.1/docs/manual/index.html] \\
+ * HTML Manual (single-page): [http://openjpa.apache.org/builds/1.0.1/apache-openjpa-1.0.1/docs/manual/manual.html] \\
+ * PDF Manual: [http://openjpa.apache.org/builds/1.0.1/apache-openjpa-1.0.1/docs/manual/manual.pdf] \\
+ * Javadocs: [http://openjpa.apache.org/builds/1.0.1/apache-openjpa-1.0.1/docs/javadoc/index.html] \\
+||
+|| Thursday, 15:45 | Merge the staged maven2 repository jars to with the official repository to rsync. This is currently a difficult process that requires the *maven-staging-plugin*, which much be built from source. The process looks something like this (executed in the root of your local OpenJPA checkout): \\
+{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
+{code}{warning}
+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>
+{code}
+{info}
+{{$PATH_TO_PRIVATE_KEY}} is the path to the private key generated for ssh. E.g. /home/yourLocalUserId/.ssh/id_dsa.
+{info} |
+
+h3. Expose a copy of known hosts to Maven
+
+|| 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
+{code} ||
+|| Solution | Rename the path and remove all spaces. ||
+
+h3. Merging local repository to remote repository in Cygwin/Windows
+
+|| Description | 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:
+* Use absolute path in the find command's root directory. \\
+Problem symptom:
+{code}
+$ 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
+{code}
+* Quote and use the drive name in the path.
+Problem symptom:
+{code}
+$ 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.)
+{code}
+* Specify the people.apache.org user id in the target property.
+Problem symptom:
+{code}
+$ 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
+{code} ||
+|| Solution | As recommended in the descriptions.
+{note}For example:
+{code}
+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 \;
+{code} {note} ||
+
+h3. Cygwin/Windows File Path
+
+|| Description | 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.||
+|| Solution | Consistently use the following naming conventions:
+* 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}}"
+ ||
+
+h3. "Too many unapproved licenses:"
+
+|| Description | 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:
+# Eclipse control files, .classpath, .project
+# User created log files ||
+|| Solution | Avoid the followings:
+# 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.
+# Don't create, directly or indirectly, any files under the release build tree.
+ ||
+
+h2. 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)



Mime
View raw message