Author: buildbot
Date: Wed Sep 30 17:03:02 2015
New Revision: 967325
Log:
Staging update by buildbot for openjpa
Added:
websites/staging/openjpa/trunk/content/openjpa-2.3.x.html
websites/staging/openjpa/trunk/content/openjpa-2.4.x.html
Removed:
websites/staging/openjpa/trunk/content/openjpa-2.4.0.html
Modified:
websites/staging/openjpa/trunk/content/ (props changed)
websites/staging/openjpa/trunk/content/2.1-roadmap.html
websites/staging/openjpa/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).html
websites/staging/openjpa/trunk/content/apidiscussionfollowup.html
websites/staging/openjpa/trunk/content/apply-an-eclipse-patch.html
websites/staging/openjpa/trunk/content/architecture-notes.html
websites/staging/openjpa/trunk/content/automated-builds.html
websites/staging/openjpa/trunk/content/banner.html
websites/staging/openjpa/trunk/content/bean-validation-primer.html
websites/staging/openjpa/trunk/content/begin-using-openjpa---the-basics.html
websites/staging/openjpa/trunk/content/beginners-performance-guide.html
websites/staging/openjpa/trunk/content/best-practices.html
websites/staging/openjpa/trunk/content/build-and-runtime-dependencies.html
websites/staging/openjpa/trunk/content/buildbot.tips.n.techniques.html
websites/staging/openjpa/trunk/content/building-and-running-openbooks.html
websites/staging/openjpa/trunk/content/building.html
websites/staging/openjpa/trunk/content/coding-standards.html
websites/staging/openjpa/trunk/content/community.html
websites/staging/openjpa/trunk/content/consumers.html
websites/staging/openjpa/trunk/content/detached.state.serialization.html
websites/staging/openjpa/trunk/content/development-process.html
websites/staging/openjpa/trunk/content/development.html
websites/staging/openjpa/trunk/content/documentation.html
websites/staging/openjpa/trunk/content/domain-model-browser.html
websites/staging/openjpa/trunk/content/downloads-nightly.html
websites/staging/openjpa/trunk/content/downloads.html
websites/staging/openjpa/trunk/content/embeddable-samples.html
websites/staging/openjpa/trunk/content/enhancement-with-ant.html
websites/staging/openjpa/trunk/content/enhancement-with-eclipse.html
websites/staging/openjpa/trunk/content/enhancement-with-maven.html
websites/staging/openjpa/trunk/content/entity-enhancement.html
websites/staging/openjpa/trunk/content/faq.html
websites/staging/openjpa/trunk/content/fetch-statistics.html
websites/staging/openjpa/trunk/content/findbugs-presentation-notes.html
websites/staging/openjpa/trunk/content/found-a-bug.html
websites/staging/openjpa/trunk/content/get-involved.html
websites/staging/openjpa/trunk/content/getting-started.html
websites/staging/openjpa/trunk/content/index.html
websites/staging/openjpa/trunk/content/integration.html
websites/staging/openjpa/trunk/content/intro.html
websites/staging/openjpa/trunk/content/jconsole-datacache-plugin.html
websites/staging/openjpa/trunk/content/jest-examples.html
websites/staging/openjpa/trunk/content/jest-representation.html
websites/staging/openjpa/trunk/content/jest-syntax.html
websites/staging/openjpa/trunk/content/jest-transaction.html
websites/staging/openjpa/trunk/content/jest-usage.html
websites/staging/openjpa/trunk/content/jpa-2.0-development-process.html
websites/staging/openjpa/trunk/content/jpa-2.0-iterations.html
websites/staging/openjpa/trunk/content/jpa-2.0-presentations.html
websites/staging/openjpa/trunk/content/jpa-2.0-roadmap.html
websites/staging/openjpa/trunk/content/jpa-2.0-tasks.html
websites/staging/openjpa/trunk/content/jpa-2.0-test-coverage.html
websites/staging/openjpa/trunk/content/jpa-2.1-development-process.html
websites/staging/openjpa/trunk/content/jpa-2.1-roadmap.html
websites/staging/openjpa/trunk/content/jpa-2.1-tasks.html
websites/staging/openjpa/trunk/content/jpa-2.1-test-coverage.html
websites/staging/openjpa/trunk/content/jpa-m2-demo.html
websites/staging/openjpa/trunk/content/jpa-specification-development.html
websites/staging/openjpa/trunk/content/jsr-317-20081031-public-draft-tasks.html
websites/staging/openjpa/trunk/content/license.html
websites/staging/openjpa/trunk/content/logo-contest.html
websites/staging/openjpa/trunk/content/mailing-lists.html
websites/staging/openjpa/trunk/content/migration-tool.html
websites/staging/openjpa/trunk/content/obtaining.html
websites/staging/openjpa/trunk/content/openbooks---featuring-jpa-2.0.html
websites/staging/openjpa/trunk/content/openjpa+email.html
websites/staging/openjpa/trunk/content/openjpa-2.0.0-beta-2.html
websites/staging/openjpa/trunk/content/openjpa-2.0.0-beta-3.html
websites/staging/openjpa/trunk/content/openjpa-2.0.0-beta.html
websites/staging/openjpa/trunk/content/openjpa-2.0.0-early-access-2.html
websites/staging/openjpa/trunk/content/openjpa-2.0.0-milestone-3.html
websites/staging/openjpa/trunk/content/openjpa-2.0.0.html
websites/staging/openjpa/trunk/content/openjpa-2.0.1.html
websites/staging/openjpa/trunk/content/openjpa-2.1.0.html
websites/staging/openjpa/trunk/content/openjpa-2.2.0.html
websites/staging/openjpa/trunk/content/openjpa-development-resources.html
websites/staging/openjpa/trunk/content/openjpa-logo-contest---round-1.html
websites/staging/openjpa/trunk/content/openjpa-logo-contest---round-2.html
websites/staging/openjpa/trunk/content/openjpa-logo-contest---run-off.html
websites/staging/openjpa/trunk/content/openjpa-release-policy.html
websites/staging/openjpa/trunk/content/openjpa-up-close-and-personal.html
websites/staging/openjpa/trunk/content/openjpaeclipseenhancementbuilder.html
websites/staging/openjpa/trunk/content/openjpaeclipseinstallation.html
websites/staging/openjpa/trunk/content/openjpaeclipsetoolingdevandbuild.html
websites/staging/openjpa/trunk/content/opentrader.html
websites/staging/openjpa/trunk/content/opentraderarchitecture.html
websites/staging/openjpa/trunk/content/opentraderbuild.html
websites/staging/openjpa/trunk/content/opentraderclient.html
websites/staging/openjpa/trunk/content/opentradercommunication.html
websites/staging/openjpa/trunk/content/opentraderdeploy.html
websites/staging/openjpa/trunk/content/opentraderenvironment.html
websites/staging/openjpa/trunk/content/opentraderserver.html
websites/staging/openjpa/trunk/content/overview.html
websites/staging/openjpa/trunk/content/performance-guide.html
websites/staging/openjpa/trunk/content/powered-by.html
websites/staging/openjpa/trunk/content/privacy-policy.html
websites/staging/openjpa/trunk/content/publishing-serp-to-maven-central-repository.html
websites/staging/openjpa/trunk/content/query-notes.html
websites/staging/openjpa/trunk/content/quick-start.html
websites/staging/openjpa/trunk/content/recovering-from-a-vetoed-release.html
websites/staging/openjpa/trunk/content/related-projects.html
websites/staging/openjpa/trunk/content/release-artifact-locations.html
websites/staging/openjpa/trunk/content/release-management.html
websites/staging/openjpa/trunk/content/release-setup.html
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.2.x-(old-scp-steps).html
websites/staging/openjpa/trunk/content/running-openjpa-examples.html
websites/staging/openjpa/trunk/content/running-the-sun-tck-for-jpa.html
websites/staging/openjpa/trunk/content/runtime-enhancement.html
websites/staging/openjpa/trunk/content/samples.html
websites/staging/openjpa/trunk/content/sampletemplate.html
websites/staging/openjpa/trunk/content/sidenav-community.html
websites/staging/openjpa/trunk/content/sidenav-development.html
websites/staging/openjpa/trunk/content/sidenav-overview.html
websites/staging/openjpa/trunk/content/sidenav-quick-links.html
websites/staging/openjpa/trunk/content/site-index.html
websites/staging/openjpa/trunk/content/source-code.html
websites/staging/openjpa/trunk/content/testing.html
websites/staging/openjpa/trunk/content/thanks.html
websites/staging/openjpa/trunk/content/tips-n-techniques.html
websites/staging/openjpa/trunk/content/tools.html
websites/staging/openjpa/trunk/content/troubleshoot.html
websites/staging/openjpa/trunk/content/update-release-text-files.html
websites/staging/openjpa/trunk/content/using-criteria-api-in-daytrader.html
websites/staging/openjpa/trunk/content/verifying-release-signatures.html
websites/staging/openjpa/trunk/content/websphere-application-server.html
websites/staging/openjpa/trunk/content/whither-openjpa.html
websites/staging/openjpa/trunk/content/writing-test-cases-for-openjpa.html
Propchange: websites/staging/openjpa/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Sep 30 17:03:02 2015
@@ -1 +1 @@
-1706082
+1706084
Modified: websites/staging/openjpa/trunk/content/2.1-roadmap.html
==============================================================================
--- websites/staging/openjpa/trunk/content/2.1-roadmap.html (original)
+++ websites/staging/openjpa/trunk/content/2.1-roadmap.html Wed Sep 30 17:03:02
2015
@@ -145,12 +145,23 @@ limitations under the License.
</td>
<td valign="top" width="100%"
style="overflow:hidden;">
<div class="wiki-content">
- <p><a
name="2.1Roadmap-OpenJPA2.1Roadmap"></a></p>
-<h1 id="openjpa-21-roadmap">OpenJPA 2.1 Roadmap</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a name="2.1Roadmap-OpenJPA2.1Roadmap"></a></p>
+<h1 id="openjpa-21-roadmap">OpenJPA 2.1 Roadmap<a class="headerlink"
href="#openjpa-21-roadmap" title="Permanent link">¶</a></h1>
<p>We'll try to maintain this page with delivered and planned features for the
OpenJPA 2.1.0 release, so check back often.</p>
<p><a name="2.1Roadmap-PlannedFeatures"></a></p>
-<h2 id="planned-features">Planned Features</h2>
+<h2 id="planned-features">Planned Features<a class="headerlink"
href="#planned-features" title="Permanent link">¶</a></h2>
<ul>
<li>Built-in connection pooling for Java SE applications<ul>
<li>Inclusion of commons-dbcp in openjpa-all.jar and the binary
distribution</li>
@@ -185,14 +196,14 @@ binary distribution</li>
</li>
</ul>
<p><a name="2.1Roadmap-MigrationIssues"></a></p>
-<h1 id="migration-issues">Migration Issues</h1>
+<h1 id="migration-issues">Migration Issues<a class="headerlink"
href="#migration-issues" title="Permanent link">¶</a></h1>
<ul>
<li>This release will officially <em>drop support for Java SE 5</em>. Anyone
requiring Java SE 5 support will have to continue using OpenJPA 2.0.x,
which is fully JPA 2.0 compliant.</li>
</ul>
<p><a name="2.1Roadmap-ReleasePlan"></a></p>
-<h1 id="release-plan">Release Plan</h1>
+<h1 id="release-plan">Release Plan<a class="headerlink" href="#release-plan"
title="Permanent link">¶</a></h1>
<p>A <a href="https://svn.apache.org/repos/asf/openjpa/branches/2.1.x/";>2.1.x
branch</a>
is available in SVN and 2.1.0 release preparations are underway. The
OpenJPA team is planning to deliver a 2.1.0 release in late January, 2011.</p>
Modified:
websites/staging/openjpa/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).html
==============================================================================
---
websites/staging/openjpa/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).html
(original)
+++
websites/staging/openjpa/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).html
Wed Sep 30 17:03:02 2015
@@ -145,8 +145,19 @@ limitations under the License.
</td>
<td valign="top" width="100%"
style="overflow:hidden;">
<div class="wiki-content">
- <p><a
name="apache-nexus-release-process-(1.2.x-2.1.x)"></a></p>
-<h1 id="release-steps-for-openjpa-12x-2x">Release Steps for OpenJPA 1.2.x -
2.x</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a name="apache-nexus-release-process-(1.2.x-2.1.x)"></a></p>
+<h1 id="release-steps-for-openjpa-12x-2x">Release Steps for OpenJPA 1.2.x -
2.x<a class="headerlink" href="#release-steps-for-openjpa-12x-2x"
title="Permanent link">¶</a></h1>
<p>We're starting to move our builds over to using the Apache Nexus repository
(repository.apache.org) for releasing SNAPSHOT and release artifacts.
More details on releasing artifacts and using Nexus can be found on the Maven
website at - <a
href="http://maven.apache.org/developers/release/apache-release.html";>http://maven.apache.org/developers/release/apache-release.html</a></p>
<ol>
@@ -165,9 +176,7 @@ More details on releasing artifacts and
</li>
<li>Use Maven 2.2.1 or later (2.2.1 is required for release signing fixes)</li>
<li>Make sure the <a
href="http://openjpa.apache.org/release-setup.html";>Release Setup</a> steps
have been performed.</li>
-<li>
-<p>To verify:</p>
-<div class="codehilite"><pre><span class="p">[</span><span
class="n">root</span><span class="p">@</span><span class="n">vega</span> <span
class="n">workspace</span><span class="p">]</span># <span class="n">mvn</span>
<span class="o">-</span><span class="n">v</span>
+<li>To verify:<div class="codehilite"><pre><span class="p">[</span><span
class="n">root</span><span class="p">@</span><span class="n">vega</span> <span
class="n">workspace</span><span class="p">]</span># <span class="n">mvn</span>
<span class="o">-</span><span class="n">v</span>
<span class="n">Apache</span> <span class="n">Maven</span> 2<span
class="p">.</span>2<span class="p">.</span>1 <span class="p">(</span><span
class="n">r801777</span><span class="p">;</span> 2009<span
class="o">-</span>08<span class="o">-</span>06 14<span
class="p">:</span>16<span class="p">:</span>01<span class="o">-</span>0500<span
class="p">)</span>
<span class="n">Java</span> <span class="n">version</span><span
class="p">:</span> 1<span class="p">.</span>6<span class="p">.</span>0<span
class="n">_43</span>
<span class="n">Java</span> <span class="n">home</span><span
class="p">:</span> <span class="o">/</span><span class="n">opt</span><span
class="o">/</span><span class="n">java</span><span class="o">/</span><span
class="n">sun</span><span class="o">/</span><span class="n">jdk6_43</span><span
class="o">/</span><span class="n">jre</span>
@@ -200,9 +209,7 @@ More details on releasing artifacts and
<li>openjpa-project/RELEASE.NOTES.html</li>
</ul>
</li>
-<li>
-<p>Commit any changes back to svn - </p>
-<div class="codehilite"><pre>$ <span class="n">svn</span> <span
class="n">commit</span> <span class="o">-</span><span class="n">m</span>
"<span class="n">Updating</span> <span class="n">files</span> <span
class="k">for</span> <span class="n">release</span><span
class="p">.</span>"
+<li>Commit any changes back to svn - <div class="codehilite"><pre>$ <span
class="n">svn</span> <span class="n">commit</span> <span
class="o">-</span><span class="n">m</span> "<span
class="n">Updating</span> <span class="n">files</span> <span
class="k">for</span> <span class="n">release</span><span
class="p">.</span>"
</pre></div>
@@ -267,9 +274,7 @@ Simply extract and replace the jar files
<li>
<p>For new major releases (like 2.0.0 to 2.1.0)</p>
<ol>
-<li>
-<p>Create a sub-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. It also provides a
future maintenance branch (like 2.0.x.) A branch can be made by running:</p>
-<div class="codehilite"><pre>$ <span class="n">mvn</span> <span
class="n">release</span><span class="p">:</span><span class="n">branch</span>
<span class="o">-</span><span class="n">DbranchName</span><span
class="p">=</span>2<span class="p">.</span>0<span class="p">.</span><span
class="n">x</span> <span class="o">-</span><span
class="n">Dusername</span><span class="p">=</span><span
class="n">svn</span><span class="p">.</span><span class="n">user</span> <span
class="o">-</span><span class="n">Dpassword</span><span class="p">=</span><span
class="n">svn</span><span class="p">.</span><span class="n">password</span>
+<li>Create a sub-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. It also provides a
future maintenance branch (like 2.0.x.) A branch can be made by running:<div
class="codehilite"><pre>$ <span class="n">mvn</span> <span
class="n">release</span><span class="p">:</span><span class="n">branch</span>
<span class="o">-</span><span class="n">DbranchName</span><span
class="p">=</span>2<span class="p">.</span>0<span class="p">.</span><span
class="n">x</span> <span class="o">-</span><span
class="n">Dusername</span><span class="p">=</span><span
class="n">svn</span><span class="p">.</span><span class="n">user</span> <span
class="o">-</span><span class="n">Dpassword</span><span class="p">=</span><span
class="n">svn</span><span class="p">.</span><span class="n">password</sp
an>
</pre></div>
@@ -298,9 +303,7 @@ Simply extract and replace the jar files
<li>Release version - take the default - (default 2.0.1) </li>
<li>SCM release tag - <em>DO NOT TAKE THE DEFAULT</em> - (default
openjpa-parent-2.0.1): : 2.0.1</li>
<li>New development version - take the default - (default 2.0.2-SNAPSHOT) </li>
-<li>
-<p><em>optional</em> if you have not specified a GPG passphrase in
settings.xml you will be prompted for it. </p>
-<div class="codehilite"><pre> $ <span class="n">mvn</span> <span
class="o">-</span><span class="n">Papache</span><span class="o">-</span><span
class="n">release</span> <span class="n">release</span><span
class="p">:</span><span class="n">prepare</span> <span class="o">-</span><span
class="n">DdryRun</span><span class="p">=</span><span class="n">true</span>
+<li><em>optional</em> if you have not specified a GPG passphrase in
settings.xml you will be prompted for it. <div class="codehilite"><pre> $
<span class="n">mvn</span> <span class="o">-</span><span
class="n">Papache</span><span class="o">-</span><span class="n">release</span>
<span class="n">release</span><span class="p">:</span><span
class="n">prepare</span> <span class="o">-</span><span
class="n">DdryRun</span><span class="p">=</span><span class="n">true</span>
</pre></div>
@@ -398,9 +401,7 @@ $ <span class="n">mvn</span> <span class
<p>Verify the HTML links in staging-site/index.html are correct</p>
<ol>
<li>Login to people.apache.org</li>
-<li>
-<p>Edit public_html/openjpa/[release]/staging-site/index.html and updates the
followings:</p>
-<div class="codehilite"><pre><span class="nt"><a</span> <span
class="na">href=</span><span class="s">"downloads/"</span><span
class="nt">></span>Downloads<span class="nt"></a></span>
+<li>Edit public_html/openjpa/[release]/staging-site/index.html and updates the
followings:<div class="codehilite"><pre><span class="nt"><a</span> <span
class="na">href=</span><span class="s">"downloads/"</span><span
class="nt">></span>Downloads<span class="nt"></a></span>
to
<span class="nt"><a</span> <span class="na">href=</span><span
class="s">"apache-openjpa/downloads/"</span><span
class="nt">></span>Downloads<span class="nt"></a></span>
@@ -648,9 +649,7 @@ $ <span class="n">rm</span> <span class=
<ul>
<li>Update the new SNAPSHOT manual and javadoc links</li>
<li>Add a newly created release entry </li>
-<li>
-<p>Update SNAPSHOT documentation source URL in <a
href="https://svn.apache.org/repos/asf/openjpa/site/trunk/content/.htaccess";>https://svn.apache.org/repos/asf/openjpa/site/trunk/content/.htaccess</a>.
For example:</p>
-<div class="codehilite"><pre><span class="n">From</span>
+<li>Update SNAPSHOT documentation source URL in <a
href="https://svn.apache.org/repos/asf/openjpa/site/trunk/content/.htaccess";>https://svn.apache.org/repos/asf/openjpa/site/trunk/content/.htaccess</a>.
For example:<div class="codehilite"><pre><span class="n">From</span>
<span class="n">Redirect</span> <span class="n">Permanent</span> <span
class="o">/</span><span class="n">builds</span><span class="o">/</span><span
class="n">apache</span><span class="o">-</span><span
class="n">openjpa</span><span class="o">-</span>2<span class="p">.</span>2<span
class="p">.</span>2<span class="o">-</span><span class="n">SNAPSHOT</span><span
class="o">/</span><span class="n">docs</span> <span
class="n">http</span><span class="p">:</span><span class="o">//</span><span
class="n">ci</span><span class="p">.</span><span class="n">apache</span><span
class="p">.</span><span class="n">org</span><span class="o">/</span><span
class="n">projects</span><span class="o">/</span><span
class="n">openjpa</span><span class="o">/</span>2<span class="p">.</span>2<span
class="p">.</span><span class="n">x</span>
<span class="n">to</span>
<span class="n">Redirect</span> <span class="n">Permanent</span> <span
class="o">/</span><span class="n">builds</span><span class="o">/</span><span
class="n">apache</span><span class="o">-</span><span
class="n">openjpa</span><span class="o">-</span>2<span class="p">.</span>2<span
class="p">.</span>3<span class="o">-</span><span class="n">SNAPSHOT</span><span
class="o">/</span><span class="n">docs</span> <span
class="n">http</span><span class="p">:</span><span class="o">//</span><span
class="n">ci</span><span class="p">.</span><span class="n">apache</span><span
class="p">.</span><span class="n">org</span><span class="o">/</span><span
class="n">projects</span><span class="o">/</span><span
class="n">openjpa</span><span class="o">/</span>2<span class="p">.</span>2<span
class="p">.</span><span class="n">x</span>
@@ -714,7 +713,7 @@ announcement.
</li>
</ol>
<p><a name="recoverFromVetoRelease"></a> </p>
-<h1 id="recovering-from-a-vetoed-release">Recovering from a vetoed release</h1>
+<h1 id="recovering-from-a-vetoed-release">Recovering from a vetoed release<a
class="headerlink" href="#recovering-from-a-vetoed-release" title="Permanent
link">¶</a></h1>
<ol>
<li>
<p>Reply to the initial vote email and prepend to the original subject -</p>
@@ -769,7 +768,7 @@ $ rm -fr <span class="cp">${</span><span
<li>Spin another release candidate!</li>
</ol>
<p><a name="verifySig"></a></p>
-<h1 id="verifying-release-signatures">Verifying release signatures</h1>
+<h1 id="verifying-release-signatures">Verifying release signatures<a
class="headerlink" href="#verifying-release-signatures" title="Permanent
link">¶</a></h1>
<p>On unix platforms the following command can be executed -</p>
<div class="codehilite"><pre>for file in `find . -type f -iname
'*.asc'`
do
Modified: websites/staging/openjpa/trunk/content/apidiscussionfollowup.html
==============================================================================
--- websites/staging/openjpa/trunk/content/apidiscussionfollowup.html (original)
+++ websites/staging/openjpa/trunk/content/apidiscussionfollowup.html Wed Sep
30 17:03:02 2015
@@ -145,7 +145,18 @@ limitations under the License.
</td>
<td valign="top" width="100%"
style="overflow:hidden;">
<div class="wiki-content">
- <p><a
name="APIDiscussionFollowUp"></a></p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a name="APIDiscussionFollowUp"></a></p>
<p>After our meeting, Patrick did some analysis of our current API and where
we might want to take it. Here are some initial observations. Please
comment as appropriate.</p>
Modified: websites/staging/openjpa/trunk/content/apply-an-eclipse-patch.html
==============================================================================
--- websites/staging/openjpa/trunk/content/apply-an-eclipse-patch.html
(original)
+++ websites/staging/openjpa/trunk/content/apply-an-eclipse-patch.html Wed Sep
30 17:03:02 2015
@@ -145,11 +145,22 @@ limitations under the License.
</td>
<td valign="top" width="100%"
style="overflow:hidden;">
<div class="wiki-content">
- <p><a
name="ApplyanEclipsePatch-ApplyanEclipsePatchtoDayTrader"></a></p>
-<h1 id="apply-an-eclipse-patch-to-daytrader">Apply an Eclipse Patch to
DayTrader</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a name="ApplyanEclipsePatch-ApplyanEclipsePatchtoDayTrader"></a></p>
+<h1 id="apply-an-eclipse-patch-to-daytrader">Apply an Eclipse Patch to
DayTrader<a class="headerlink" href="#apply-an-eclipse-patch-to-daytrader"
title="Permanent link">¶</a></h1>
<p>You can apply an Eclipse patch to DayTrader for the Criteria API changes</p>
<p><a name="ApplyanEclipsePatch-SettingupEclipse"></a></p>
-<h2 id="setting-up-eclipse">Setting up Eclipse</h2>
+<h2 id="setting-up-eclipse">Setting up Eclipse<a class="headerlink"
href="#setting-up-eclipse" title="Permanent link">¶</a></h2>
<p>First install eclipse by going to <a
href="http://www.eclipse.org";>http:/www.eclipse.org</a>
and downloading a version of it. These instructions assume version 3.5.
Unzip the downloaded file into a directory. You can start eclipse by
@@ -176,7 +187,7 @@ running eclipse.exe in the eclipse dire
<li>Select all projects and click Finish</li>
</ol>
<p><a name="ApplyanEclipsePatch-ApplyingthePatch"></a></p>
-<h2 id="applying-the-patch">Applying the Patch</h2>
+<h2 id="applying-the-patch">Applying the Patch<a class="headerlink"
href="#applying-the-patch" title="Permanent link">¶</a></h2>
<p>Replace the following files in your local file system copy of
DayTrader:</p>
<ul>
<li>the pom.xml file in the root (<em>Daytrader/branches/2.1.3</em>)
directory with <a href="artifacts/pom.xml">pom.xml</a>.</li>
Modified: websites/staging/openjpa/trunk/content/architecture-notes.html
==============================================================================
--- websites/staging/openjpa/trunk/content/architecture-notes.html (original)
+++ websites/staging/openjpa/trunk/content/architecture-notes.html Wed Sep 30
17:03:02 2015
@@ -145,7 +145,18 @@ limitations under the License.
</td>
<td valign="top" width="100%"
style="overflow:hidden;">
<div class="wiki-content">
- <p>OpenJPA Architecture
notes:</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>OpenJPA Architecture notes:</p>
<p>Design point: object persistence; ORM but other stores also supported by
the architecture</p>
<p>domain model: user's responsibility; other areas are OpenJPA</p>
Modified: websites/staging/openjpa/trunk/content/automated-builds.html
==============================================================================
--- websites/staging/openjpa/trunk/content/automated-builds.html (original)
+++ websites/staging/openjpa/trunk/content/automated-builds.html Wed Sep 30
17:03:02 2015
@@ -145,11 +145,22 @@ limitations under the License.
</td>
<td valign="top" width="100%"
style="overflow:hidden;">
<div class="wiki-content">
- <p><a
name="Automated-Builds"></a></p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a name="Automated-Builds"></a></p>
<p>We're using the Jenkins build server for continuous builds for several of
the OpenJPA code streams and some of the artifacts in the Tools subproject.</p>
<p><a name="AutomatedBuilds-JenkinsJobs-OpenJPA"></a></p>
-<h3 id="jenkins-jobs-openjpa">Jenkins Jobs - OpenJPA</h3>
+<h3 id="jenkins-jobs-openjpa">Jenkins Jobs - OpenJPA<a class="headerlink"
href="#jenkins-jobs-openjpa" title="Permanent link">¶</a></h3>
<p><a href="https://builds.apache.org/job/OpenJPA-12x/";>OpenJPA 1.2.x build
and deploy</a>
- This build runs on the Ubuntu build agents and is set up to check SVN
for updates once every hour at 45 minutes past the hour and deploy
@@ -168,17 +179,17 @@ for updates twice every hour at 0 and 30
- This build runs on the Ubuntu build agents and is set up to check SVN
for updates once a day at 06:45 (UTC) and deploy artifacts.</p>
<p><a name="AutomatedBuilds-JenkinsJobs-OpenJPATools"></a></p>
-<h3 id="jenkins-jobs-openjpa-tools">Jenkins Jobs - OpenJPA Tools</h3>
+<h3 id="jenkins-jobs-openjpa-tools">Jenkins Jobs - OpenJPA Tools<a
class="headerlink" href="#jenkins-jobs-openjpa-tools" title="Permanent
link">¶</a></h3>
<p><a href="https://builds.apache.org/job/OpenJPA-tools-trunk/";>OpenJPA Tools
trunk build and deploy</a>
- This build runs on the Ubuntu build agents and is set up to check SVN
for updates once every hour at 55 minutes past the hour and deploy
artifacts.</p>
<p><a name="AutomatedBuilds-EmailNotifications"></a></p>
-<h3 id="email-notifications">Email Notifications</h3>
+<h3 id="email-notifications">Email Notifications<a class="headerlink"
href="#email-notifications" title="Permanent link">¶</a></h3>
<p>Email notifications to commits@openjpa are generated by Jenkins for build
failures and when builds are back to normal.</p>
<p><a name="AutomatedBuilds-JenkinsInfo"></a></p>
-<h3 id="jenkins-info">Jenkins Info</h3>
+<h3 id="jenkins-info">Jenkins Info<a class="headerlink" href="#jenkins-info"
title="Permanent link">¶</a></h3>
<p>If you're interested in the Jenkins services or would like to request an
account on the server, checkout the <a
href="http://wiki.apache.org/general/Hudson";>Jenkins wiki</a>
for more information. The builds.apache.org server uses the Apache LDAP
Modified: websites/staging/openjpa/trunk/content/banner.html
==============================================================================
--- websites/staging/openjpa/trunk/content/banner.html (original)
+++ websites/staging/openjpa/trunk/content/banner.html Wed Sep 30 17:03:02 2015
@@ -145,7 +145,18 @@ limitations under the License.
</td>
<td valign="top" width="100%"
style="overflow:hidden;">
<div class="wiki-content">
- <p><a name="Banner"></a></p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a name="Banner"></a></p>
<div id="header_background">
<div id="openjpa_logo">
<a style="float:left;
