You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by re...@apache.org on 2022/07/07 09:57:07 UTC
svn commit: r1902519 [5/27] - in /jackrabbit/site/live/jcr: ./ components/ css/ fonts/ js/ ocm/ status/
Modified: jackrabbit/site/live/jcr/creating-releases.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/jcr/creating-releases.html?rev=1902519&r1=1902518&r2=1902519&view=diff
==============================================================================
--- jackrabbit/site/live/jcr/creating-releases.html (original)
+++ jackrabbit/site/live/jcr/creating-releases.html Thu Jul 7 09:57:06 2022
@@ -1,40 +1,42 @@
<!DOCTYPE html>
-
-
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.11.1 from src/site/markdown/creating-releases.md at 2022-07-05
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from src\site\markdown/creating-releases.md at 2022-05-16
+ | Rendered using Apache Maven Fluido Skin 1.9
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.9.2" />
<title>Apache Jackrabbit – Creating Releases</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.11.1.min.js"></script>
-
- <!-- Matomo -->
- <script>
- var _paq = window._paq = window._paq || [];
- _paq.push(['disableCookies']);
- _paq.push(['trackPageView']);
- _paq.push(['enableLinkTracking']);
-
- (function() {
- var u="https://analytics.apache.org";
- _paq.push(['setTrackerUrl', u+'/matomo.php']);
- _paq.push(['setSiteId', '4']);
- var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
- g.async=true; g.src=u+'/matomo.js'; s.parentNode.insertBefore(g,s);
- })();
- </script>
- <!-- End Matomo Code -->
+ <script src="./js/apache-maven-fluido-1.9.min.js"></script>
+<!-- Matomo -->
+<script>
+ var _paq = window._paq = window._paq || [];
+ /* tracker methods like "setCustomDimension" should be called before "trackPageView" */
+ /* We explicitly disable cookie tracking to avoid privacy issues */
+ _paq.push(['disableCookies']);
+ _paq.push(['trackPageView']);
+ _paq.push(['enableLinkTracking']);
+ (function() {
+ var u="https://matomo.privacy.apache.org/";
+ _paq.push(['setTrackerUrl', u+'matomo.php']);
+ _paq.push(['setSiteId', '4']);
+ var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
+ g.async=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
+ })();
+</script>
+<!-- End Matomo Code -->
</head>
<body class="topBarEnabled">
- <a class="github-fork-ribbon right-top" href="https://github.com/apache/jackrabbit" data-ribbon="Fork me on GitHub" title="Fork me on GitHub">Fork me on GitHub</a>
+ <a href="https://github.com/apache/jackrabbit">
+ <img style="position: absolute; top: 0; right: 0; border: 0; z-index: 10000;"
+ src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"
+ alt="Fork me on GitHub">
+ </a>
<header id="topbar" class="navbar navbar-fixed-top ">
<div class="navbar-inner">
<div class="container-fluid">
@@ -47,7 +49,7 @@
</a>
<ul class="nav">
<li class="dropdown">
- <a class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="index.html" title="Welcome">Welcome</a></li>
<li><a href="downloads.html" title="Downloads">Downloads</a></li>
@@ -58,7 +60,7 @@
</ul>
</li>
<li class="dropdown">
- <a class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="getting-started-with-apache-jackrabbit.html" title="Getting Started">Getting Started</a></li>
<li><a href="standalone-server.html" title="Standalone Server">Standalone Server</a></li>
@@ -73,7 +75,7 @@
</ul>
</li>
<li class="dropdown">
- <a class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="jackrabbit-team.html" title="Jackrabbit Team">Jackrabbit Team</a></li>
<li><a href="jackrabbit-roadmap.html" title="Jackrabbit Roadmap">Jackrabbit Roadmap</a></li>
@@ -83,12 +85,12 @@
<li><a href="source-repository.html" title="Source Repository">Source Repository</a></li>
<li><a href="continuous-integration.html" title="Continuous Integration">Continuous Integration</a></li>
<li><a href="website.html" title="Website">Website</a></li>
- <li><a title="Creating Releases">Creating Releases</a></li>
+ <li><a href="creating-releases.html" title="Creating Releases">Creating Releases</a></li>
<li><a href="supporting-software-attribution.html" title="Attribution">Attribution</a></li>
</ul>
</li>
<li class="dropdown">
- <a class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="https://www.apache.org/foundation/how-it-works.html" title="Introduction">Introduction</a></li>
<li><a href="https://www.apache.org/foundation/sponsorship.html" title="Sponsorship">Sponsorship</a></li>
@@ -103,7 +105,7 @@
<div class="container-fluid">
<header>
<div id="banner">
- <div class="pull-left"><div id="bannerLeft"><h1>Apache Jackrabbit Site</h1>
+ <div class="pull-left"><div id="bannerLeft"><h2>Apache Jackrabbit Site</h2>
</div>
</div>
<div class="pull-right"></div>
@@ -112,7 +114,7 @@
<div id="breadcrumbs">
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2022-07-05</li>
+ <li id="publishDate">Last Published: 2022-05-16</li>
</ul>
</div>
</header>
@@ -147,7 +149,7 @@
<li><a href="source-repository.html" title="Source Repository"><span class="none"></span>Source Repository</a></li>
<li><a href="continuous-integration.html" title="Continuous Integration"><span class="none"></span>Continuous Integration</a></li>
<li><a href="website.html" title="Website"><span class="none"></span>Website</a></li>
- <li class="active"><a><span class="none"></span>Creating Releases</a></li>
+ <li class="active"><a href="#"><span class="none"></span>Creating Releases</a></li>
<li><a href="supporting-software-attribution.html" title="Attribution"><span class="none"></span>Attribution</a></li>
<li class="nav-header">Apache Software Foundation</li>
<li><a href="https://www.apache.org/foundation/how-it-works.html" class="externalLink" title="Introduction"><span class="none"></span>Introduction</a></li>
@@ -157,6 +159,7 @@
</ul>
</nav>
<div class="well sidebar-nav">
+ <hr />
<div id="poweredBy">
<div class="clear"></div>
<div class="clear"></div>
@@ -183,280 +186,164 @@
limitations under the License.
-->
<h1>Creating Releases</h1>
-<p>This is a how to document for creating Apache Jackrabbit releases. It
-documents the current release process and needs to be updated as we move
-forward.</p>
+<p>This is a how to document for creating Apache Jackrabbit releases. It documents the current release process and needs to be updated as we move forward.</p>
<p>This applies to both Jackrabbit 2.x as well as Jackrabbit Oak releases. For Jackrabbit FileVault please use the specific documentation at <a class="externalLink" href="https://jackrabbit.apache.org/filevault/howto_release.html">https://jackrabbit.apache.org/filevault/howto_release.html</a> and <a class="externalLink" href="https://jackrabbit.apache.org/filevault-package-maven-plugin/howto_release.html">https://jackrabbit.apache.org/filevault-package-maven-plugin/howto_release.html</a> respectively.</p><section>
<h2><a name="Release_planning"></a>Release planning</h2>
-<p>Jackrabbit releases are created based on user demand and the availability
-of fixes and other requested changes. Any committer can declare their plan
-to cut a release by sending a “Apache Jackrabbit x.y.z release plan”
-message to the dev@ list. The plan should refer to Jira for the list of
-fixes to be included in the release and give a rough estimate of the
-release schedule. It's OK to revise the plan if needed. Optimally, link to
-the candidate release notes.</p>
-<p>If you're not a committer, you can send a message to the mailing list
-asking for a new release to be made. Including the list of specific fixes
-you need and a short rationale of why you need the release.</p></section><section>
+<p>Jackrabbit releases are created based on user demand and the availability of fixes and other requested changes. Any committer can declare their plan to cut a release by sending a “Apache Jackrabbit x.y.z release plan” message to the dev@ list. The plan should refer to Jira for the list of fixes to be included in the release and give a rough estimate of the release schedule. It’s OK to revise the plan if needed. Optimally, link to the candidate release notes.</p>
+<p>If you’re not a committer, you can send a message to the mailing list asking for a new release to be made. Including the list of specific fixes you need and a short rationale of why you need the release.</p></section><section>
<h2><a name="Prerequisites_for_release_managers"></a>Prerequisites for release managers</h2>
-<p>You need to be a Jackrabbit committer to prepare and perform a release, but
-anyone is welcome to help test the release candidates and comment on the
-release plans.</p>
-<p>You should have a code signing key that is included in the Jackrabbit KEYS
-file. See <a href="#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file">Appendix A</a> at the end of this page for more details.</p>
-<p>You also need to tell Maven your Apache LDAP credentials needed for
-deploying artifacts to the Nexus server at <a class="externalLink" href="https://repository.apache.org/">https://repository.apache.org/</a>.
-See <a href="#Appendix_B:_Maven_settings">Appendix B</a> for the required settings.</p></section><section>
+<p>You need to be a Jackrabbit committer to prepare and perform a release, but anyone is welcome to help test the release candidates and comment on the release plans.</p>
+<p>You should have a code signing key that is included in the Jackrabbit KEYS file. See <a href="#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file">Appendix A</a> at the end of this page for more details.</p>
+<p>You also need to tell Maven your Apache LDAP credentials needed for deploying artifacts to the Nexus server at <a class="externalLink" href="https://repository.apache.org/">https://repository.apache.org/</a>. See <a href="#Appendix_B:_Maven_settings">Appendix B</a> for the required settings.</p></section><section>
<h2><a name="Release_management_tasks"></a>Release management tasks</h2><section>
<h3><a name="Part_I:_up_to_the_release_vote"></a>Part I: up to the release vote</h3>
<ol style="list-style-type: decimal">
-<li>
-
-<p>Check the CI status of the project (<a class="externalLink" href="https://ci-builds.apache.org/job/Jackrabbit/">Jackrabbit Jenkins</a>)</p>
-</li>
-<li>
-
-<p>Consider checking the CVE database for vulnerabilities in dependencies,
-using <code>mvn org.owasp:dependency-check-maven:7.1.0:aggregate</code> (first run will be slow because CVE
-databases are downloaded and parsed). If dependencies need action, open tickets and make sure they
-are marked as candidate backports where applicable.</p>
-</li>
-<li>
-
-<p>Make sure that an appropriate version for the release is entered in Jira
-(<a class="externalLink" href="https://issues.apache.org/jira/projects/JCR?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page">Jackrabbit Jira</a>,
-<a class="externalLink" href="https://issues.apache.org/jira/projects/OAK?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page">Oak Jira</a>)
-and that all the related issues have been resolved.</p>
-</li>
-<li>
-
-<p>Create a new version in JIRA for the next release.</p>
-</li>
-<li>
-
-<p>Check for issues that have been resolved but do not have “fixVersion” set - these may need to be updated before creating the release notes (<a class="externalLink" href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20JCR%20AND%20status%20%3D%20resolved%20AND%20fixVersion%20IS%20EMPTY%20ORDER%20BY%20issuekey%20DESC%20">Jackrabbit Jira</a>, <a class="externalLink" href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20OAK%20AND%20status%20%3D%20resolved%20AND%20fixVersion%20IS%20EMPTY%20ORDER%20BY%20issuekey%20DESC%20">Oak Jira</a>).</p>
-</li>
-<li>
-
-<p>Create a <code>RELEASE-NOTES.txt</code> file in the root folder of the project to be released.
-If such a file already exists, update it for the release. See a previous
-release notes for examples of what to include. The release note report in Jira is a
-useful source of required information: Open the <a class="externalLink" href="https://issues.apache.org/jira/projects/JCR?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page">Jackrabbit Jira</a>
-or <a class="externalLink" href="https://issues.apache.org/jira/projects/OAK?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page">Oak Jira</a> page,
-click on the release, then on the “Release Notes” link on the top.
-Double-check that all version numbers in the updated Release Notes are accurate.
-When done, commit the file.</p>
-</li>
-<li>
-
-<p>If the branch is one that supports Java 8 or newer, make sure that the API docs can indeed be built with Java 8, using both <code>javadoc:javadoc</code> and <code>javadoc:aggregate</code>.
-If the branch supports Java 11 or newer, repeat this with Java 11.</p>
-</li>
-<li>
-
-<p>Make sure that the build succeeds with all Java versions it is supposed to support (trying with the earliest and latest is ok).</p>
-</li>
-<li>
-
-<p>When releasing a Jackrabbit version that will be used in Oak, make sure it
-doesn't break Oak.</p>
+<li>Check the CI status of the project (<a class="externalLink" href="https://ci-builds.apache.org/job/Jackrabbit/">Jackrabbit Jenkins</a>)</li>
+<li>Consider checking the CVE database for vulnerabilities in dependencies, using <code>mvn org.owasp:dependency-check-maven:7.1.0:aggregate</code> (first run will be slow because CVE databases are downloaded and parsed). If dependencies need action, open tickets and make sure they are marked as candidate backports where applicable.</li>
+<li>Make sure that an appropriate version for the release is entered in Jira (<a class="externalLink" href="https://issues.apache.org/jira/projects/JCR?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page">Jackrabbit Jira</a>, <a class="externalLink" href="https://issues.apache.org/jira/projects/OAK?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page">Oak Jira</a>) and that all the related issues have been resolved.</li>
+<li>Create a new version in JIRA for the next release.</li>
+<li>Check for issues that have been resolved but do not have “fixVersion” set - these may need to be updated before creating the release notes (<a class="externalLink" href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20JCR%20AND%20status%20%3D%20resolved%20AND%20fixVersion%20IS%20EMPTY%20ORDER%20BY%20issuekey%20DESC%20">Jackrabbit Jira</a>, <a class="externalLink" href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20OAK%20AND%20status%20%3D%20resolved%20AND%20fixVersion%20IS%20EMPTY%20ORDER%20BY%20issuekey%20DESC%20">Oak Jira</a>).</li>
+<li>Create a <code>RELEASE-NOTES.txt</code> file in the root folder of the project to be released. If such a file already exists, update it for the release. See a previous release notes for examples of what to include. The release note report in Jira is a useful source of required information: Open the <a class="externalLink" href="https://issues.apache.org/jira/projects/JCR?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page">Jackrabbit Jira</a> or <a class="externalLink" href="https://issues.apache.org/jira/projects/OAK?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page">Oak Jira</a> page, click on the release, then on the “Release Notes” link on the top. Double-check that all version numbers in the updated Release Notes are accurate. When done, commit the file.</li>
+<li>If the branch is one that supports Java 8 or newer, make sure that the API docs can indeed be built with Java 8, using both <code>javadoc:javadoc</code> and <code>javadoc:aggregate</code>. If the branch supports Java 11 or newer, repeat this with Java 11.</li>
+<li>Make sure that the build succeeds with all Java versions it is supposed to support (trying with the earliest and latest is ok).</li>
+<li>When releasing a Jackrabbit version that will be used in Oak, make sure it doesn’t break Oak.
<ul>
<li>Check by building the applicable Oak version using <code>mvn clean install -PintegrationTesting -Djackrabbit.version=2.x.y-SNAPSHOT</code></li>
<li>If the update does require changes in Oak, open JIRA tickets and link them to the JIRA tickets tracking the release activity.</li>
</ul>
</li>
-<li>
+<li>If this is a stable branch, review changes to export versions which should be avoided (see <a class="externalLink" href="https://issues.apache.org/jira/browse/OAK-6346">OAK-6346</a> for context). If there are indeed changes (as in the example below), see <a href="#Appendix_E:_Version_Changes">Appendix E</a>.
-<p>If this is a stable branch, review changes to export versions which should be avoided (see <a class="externalLink" href="https://issues.apache.org/jira/browse/OAK-6346">OAK-6346</a> for context). If there are indeed changes (as in the example below), see <a href="#Appendix_E:_Version_Changes">Appendix E</a>.</p>
-
-<div class="source"><pre class="prettyprint linenums"><code># Oak 1.8 as of November 2018
+<div class="source">
+<div class="source"><pre class="prettyprint linenums"># Oak 1.8 as of November 2018
git diff jackrabbit-oak-1.8.0 | grep -i "@Version" -B 6
-@Version("1.5.0")
+@Version("1.6.0")
-</code></pre></div>
-</li>
-<li>
-
-<p>On the other hand, if this is a release from trunk, carefully review all
-export versions and check that no change introduces new dependencies on
-Guava (see <a class="externalLink" href="https://issues.apache.org/jira/browse/OAK-7182">OAK-7182</a>)</p>
-</li>
-<li>
-
-<p>If this is a release with Java 7 or older, make sure that your <code>MAVEN_OPTS</code> contain <code>-Dhttps.protocols=TLSv1.2</code>.</p>
-</li>
-<li>
-
-<p>When doing “stable” release (even-numbered), check that we do not have
-dependencies to unstable releases. In particular, stable releases of Oak
-should not reference unstable Jackrabbit releases (if this is the case,
-a new stable Jackrabbit release might be required in order to proceed).</p>
+</pre></div></div>
</li>
-<li>
-
-<p>Build and deploy the release artifacts with Maven. See <a href="#Steps_to_build_the_release_artifacts">below</a> for the exact steps.</p>
-</li>
-<li>
-
-<p>Mark the version as released in Jira: <a class="externalLink" href="https://issues.apache.org/jira/plugins/servlet/project-config/JCR/versions">Jackrabbit Jira</a>,
-<a class="externalLink" href="https://issues.apache.org/jira/plugins/servlet/project-config/OAK/versions">Oak Jira</a>. You'll see all the defined project versions. From the settings menu, choose ‘Release’ on the version.</p>
-</li>
-<li>
-
-<p>Do a sanity check that the <a class="externalLink" href="https://repository.apache.org/index.html#stagingRepositories">staged repository</a> on repository.apache.org contains all artifacts (~19 projects for Jackrabbit).</p>
-</li>
-<li>
-
-<p>Close the staged repository, giving it a meaningful name, such as “Apache Jackrabbit 2.x.y RC”</p>
-</li>
-<li>
-
-<p>Upload the artifacts to <a class="externalLink" href="https://dist.apache.org/repos/dist/dev/jackrabbit/">https://dist.apache.org/repos/dist/dev/jackrabbit/</a> as follows:</p>
+<li>On the other hand, if this is a release from trunk, carefully review all export versions and check that no change introduces new dependencies on Guava (see <a class="externalLink" href="https://issues.apache.org/jira/browse/OAK-7182">OAK-7182</a>)</li>
+<li>If this is a release with Java 7 or older, make sure that your <code>MAVEN_OPTS</code> contain <code>-Dhttps.protocols=TLSv1.2</code>.</li>
+<li>When doing “stable” release (even-numbered), check that we do not have dependencies to unstable releases. In particular, stable releases of Oak should not reference unstable Jackrabbit releases (if this is the case, a new stable Jackrabbit release might be required in order to proceed).</li>
+<li>Build and deploy the release artifacts with Maven. See <a href="#Steps_to_build_the_release_artifacts">below</a> for the exact steps.</li>
+<li>Mark the version as released in Jira: <a class="externalLink" href="https://issues.apache.org/jira/plugins/servlet/project-config/JCR/versions">Jackrabbit Jira</a>, <a class="externalLink" href="https://issues.apache.org/jira/plugins/servlet/project-config/OAK/versions">Oak Jira</a>. You’ll see all the defined project versions. From the settings menu, choose ‘Release’ on the version.</li>
+<li>Do a sanity check that the <a class="externalLink" href="https://repository.apache.org/index.html#stagingRepositories">staged repository</a> on repository.apache.org contains all artifacts (~19 projects for Jackrabbit).</li>
+<li>Close the staged repository, giving it a meaningful name, such as “Apache Jackrabbit 2.x.y RC”</li>
+<li>Upload the artifacts to <a class="externalLink" href="https://dist.apache.org/repos/dist/dev/jackrabbit/">https://dist.apache.org/repos/dist/dev/jackrabbit/</a> as follows:
-<div class="source"><pre class="prettyprint linenums"><code># TARGET - where https://dist.apache.org/repos/dist/dev/jackrabbit/ is checked out
+<div class="source">
+<div class="source"><pre class="prettyprint linenums"># TARGET - where https://dist.apache.org/repos/dist/dev/jackrabbit/ is checked out
# SOURCE - where the release was built
-</code></pre></div>
+</pre></div></div>
+
<p>For Jackrabbit:</p>
-<div class="source"><pre class="prettyprint linenums"><code>cd $TARGET
+<div class="source">
+<div class="source"><pre class="prettyprint linenums">cd $TARGET
scp -r $SOURCE/target/checkout/target/$version $version
svn add $version
svn commit -m "Apache Jackrabbit $version release candidate" $version
-</code></pre></div>
+</pre></div></div>
+
<p>For Oak:</p>
-<div class="source"><pre class="prettyprint linenums"><code>cd $TARGET
+<div class="source">
+<div class="source"><pre class="prettyprint linenums">cd $TARGET
scp -r $SOURCE/target/checkout/target/$version oak/$version
svn add oak/$version
svn commit -m "Apache Jackrabbit Oak $version release candidate" oak/$version
-</code></pre></div>
+</pre></div></div>
</li>
<li>
<p>Find the vote template (<code>./target/checkout/target/vote.txt</code>) generated by the Maven build and follow the instructions to verify the build yourself</p>
</li>
-<li>
-
-<p>Start the vote thread by emailing the applicable mailing list (<a class="externalLink" href="mailto:dev@jackrabbit.apache.org?subject=%5BVOTE%5D%20Release%20Apache%20Jackrabbit%20x.y.z">Jackrabbit</a>, <a class="externalLink" href="mailto:oak-dev@jackrabbit.apache.org?subject=%5BVOTE%5D%20Release%20Apache%20Jackrabbit%20Oak%20x.y.z">Oak</a>)</p>
-</li>
-<li>
-
-<p>Wait 72 hours (we usually allow three business days, so be careful when a weekend is ahead)</p>
-</li>
+<li>Start the vote thread by emailing the applicable mailing list (<a class="externalLink" href="mailto:dev@jackrabbit.apache.org?subject=%5BVOTE%5D%20Release%20Apache%20Jackrabbit%20x.y.z">Jackrabbit</a>, <a class="externalLink" href="mailto:oak-dev@jackrabbit.apache.org?subject=%5BVOTE%5D%20Release%20Apache%20Jackrabbit%20Oak%20x.y.z">Oak</a>)</li>
+<li>Wait 72 hours (we usually allow three business days, so be careful when a weekend is ahead)</li>
</ol></section><section>
<h3><a name="Part_II:_after_the_release_vote"></a>Part II: after the release vote</h3>
<p>If the vote fails (easy case first) remove the tag from source control, drop the staged repository, revert the version release in Jira, and announce that the vote has failed by replying to the vote email.</p>
<p>Otherwise:</p>
<ol style="list-style-type: decimal">
-<li>
+<li>Close the vote by publishing the results, replying to the original vote mail with a subject line of “[RESULT] [VOTE] Release Apache Jackrabbit …”.</li>
+<li>Copy the release candidate from dev/jackrabbit to release/jackrabbit in <a class="externalLink" href="https://dist.apache.org/repos/dist/">https://dist.apache.org/repos/dist/</a> (for Jackrabbit, <code>version</code> is just the version number, for Oak it is prefixed with <code>oak/</code>, reflecting the directory structure) – <b>be careful to properly set the version variable!!!</b>
-<p>Close the vote by publishing the results, replying to the original vote mail with a subject line of “[RESULT] [VOTE] Release Apache Jackrabbit …”.</p>
+<div class="source">
+<div class="source"><pre class="prettyprint linenums">[ "x$version" = "x" ] || svn move -m "Apache Jackrabbit $version" \
+https://dist.apache.org/repos/dist/dev/jackrabbit/$version \
+https://dist.apache.org/repos/dist/release/jackrabbit/$version
+</pre></div></div>
</li>
<li>
-<p>Copy the release candidate from dev/jackrabbit to release/jackrabbit in <a class="externalLink" href="https://dist.apache.org/repos/dist/">https://dist.apache.org/repos/dist/</a> (for Jackrabbit, <code>version</code> is just the version number, for Oak it is prefixed with <code>oak/</code>, reflecting the directory structure) – <b>be careful to properly set the version variable!!!</b></p>
-
-<div class="source"><pre class="prettyprint linenums"><code> [ "x$version" = "x" ] || svn move -m "Apache Jackrabbit $version" \
- https://dist.apache.org/repos/dist/dev/jackrabbit/$version \
- https://dist.apache.org/repos/dist/release/jackrabbit/$version
-</code></pre></div>
+<p>Delete any older releases from the same branch (they’re automatically archived)</p>
</li>
-<li>
-
-<p>Delete any older releases from the same branch (they're automatically archived)</p>
-</li>
-<li>
-
-<p>Release the <a class="externalLink" href="https://repository.apache.org/index.html#stagingRepositories">staged repository</a> for synchronization to Maven central.</p>
+<li>Release the <a class="externalLink" href="https://repository.apache.org/index.html#stagingRepositories">staged repository</a> for synchronization to Maven central.
<ul>
<li>make sure this step actually succeeded (we have seen a case where it failed and a retry was needed)</li>
</ul>
</li>
-<li>
-
-<p>Close all the issues included in the release: <a class="externalLink" href="https://issues.apache.org/jira/projects/JCR?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=released">Jackrabbit Jira</a> or <a class="externalLink" href="https://issues.apache.org/jira/projects/OAK?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=released">Oak Jira</a> -> Choose the released version -> select “View in Issue Navigator”. From the issue list you have the option to bulk update all of the included issues. Just ‘Transition Issues’ from ‘Resolved’ to ‘Closed’ and you are done!</p>
-</li>
-<li>
-
-<p>Update the Jackrabbit web site to point to the new release (<a class="externalLink" href="https://svn.apache.org/repos/asf/jackrabbit/site/trunk/">SVN</a>) (the date should be the day when the release was finished).</p>
+<li>Close all the issues included in the release: <a class="externalLink" href="https://issues.apache.org/jira/projects/JCR?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=released">Jackrabbit Jira</a> or <a class="externalLink" href="https://issues.apache.org/jira/projects/OAK?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=released">Oak Jira</a> -> Choose the released version -> select “View in Issue Navigator”. From the issue list you have the option to bulk update all of the included issues. Just ‘Transition Issues’ from ‘Resolved’ to ‘Closed’ and you are done!</li>
+<li>Update the Jackrabbit web site to point to the new release (<a class="externalLink" href="https://svn.apache.org/repos/asf/jackrabbit/site/trunk/">SVN</a>) (the date should be the day when the release was finished).
<ul>
<li>add an entry to <code>index.md</code></li>
<li>update <code>downloads.md</code> (see <a href="#Creating_Markdown_for_Downloads_Page">below</a>) - while doing so please a) remove obsoleted entries, and b) move new entries for Jackrabbit and/or Oak to the top)</li>
-<li>don't forget to deploy the site (<code>mvn site-deploy</code>)</li>
+<li>don’t forget to deploy the site (<code>mvn site-deploy</code>)</li>
</ul>
</li>
-<li>
-
-<p>If the release was a Jackrabbit release used in Oak, make sure to also update the dependency (and potentially the Javadoc link) in oak-parent/pom.xml (example: <a class="externalLink" href="https://issues.apache.org/jira/browse/OAK-4743">OAK-4743</a> - the current mapping is Jackrabbit 2.20 -> Oak trunk and Oak 1.22, Jackrabbit 2.16 -> Oak 1.8, Jackrabbit 2.14 -> Oak 1.6, Jackrabbit 2.12 -> Oak 1.4)</p>
-</li>
-<li>
-
-<p>If the release was an Oak release used in Jackrabbit (for jackrabbit-api), make sure to also update the dependency in jackrabbit-parent/pom.xml (example: <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR-4492">JCR-4492</a> - the current mapping is Oak latest stable -> Jackrabbit trunk and 2.20)</p>
-</li>
-<li>
-
-<p>If the release was a stable release for which we publish API docs (such as Jackrabbit), consider updating the live site (<a class="externalLink" href="https://svn.apache.org/repos/asf/jackrabbit/site/live/">https://svn.apache.org/repos/asf/jackrabbit/site/live/</a> - when producing the API docs, use a checkout of the actual release, specify an English locale (-Dlocale=en) and try to pick the right JDK version to minimize changes over the previously checked in docs).</p>
-</li>
-<li>
-
-<p>If the release was a stable release that is used for the baseline check in trunk (right now: Jackrabbit 2.20 and Oak 1.22), update trunk accordingly (example: <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR-4312">JCR-4312</a>)</p>
-</li>
-<li>
-
-<p>Check that all subprojects now have the correct version; if not, fix them (for instance, oak-doc and oak-doc-railroad-macro are not in the reactor pom and therefore not updated)</p>
-</li>
-<li>
-
-<p>Send a release announcement to the
-<a class="externalLink" href="mailto:announce@apache.org,announce@jackrabbit.apache.org,users@jackrabbit.apache.org,dev@jackrabbit.apache.org,oak-dev@jackrabbit.apache.org?subject=%5BANNOUNCE%5D%20Apache%20Jackrabbit%20...%20released">applicable mailing lists</a>
-once the web site and download mirrors have been synced (template generated in <code>./target/checkout/target/announcement.txt</code> – note that mirrors may need up to 12 hours!).
-Please note the announce mails needs to be sent from an @apache.org address.
-In case you are using a mailbox other than apache mailbox (such as gmail) to send mails for your apache address, make sure to send them in plain text format.
-(Warning: sending the announcement too early may cause it to be rejected for <a class="externalLink" href="mailto:announce@apache.org">announce@apache.org</a>)</p>
-</li>
+<li>If the release was a Jackrabbit release used in Oak, make sure to also update the dependency (and potentially the Javadoc link) in oak-parent/pom.xml (example: <a class="externalLink" href="https://issues.apache.org/jira/browse/OAK-4743">OAK-4743</a> - the current mapping is Jackrabbit 2.20 -> Oak trunk and Oak 1.22, Jackrabbit 2.16 -> Oak 1.8, Jackrabbit 2.14 -> Oak 1.6, Jackrabbit 2.12 -> Oak 1.4)</li>
+<li>If the release was an Oak release used in Jackrabbit (for jackrabbit-api), make sure to also update the dependency in jackrabbit-parent/pom.xml (example: <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR-4492">JCR-4492</a> - the current mapping is Oak latest stable -> Jackrabbit trunk and 2.20)</li>
+<li>If the release was a stable release for which we publish API docs (such as Jackrabbit), consider updating the live site (<a class="externalLink" href="https://svn.apache.org/repos/asf/jackrabbit/site/live/">https://svn.apache.org/repos/asf/jackrabbit/site/live/</a> - when producing the API docs, use a checkout of the actual release, specify an English locale (-Dlocale=en) and try to pick the right JDK version to minimize changes over the previously checked in docs).</li>
+<li>If the release was a stable release that is used for the baseline check in trunk (right now: Jackrabbit 2.20 and Oak 1.22), update trunk accordingly (example: <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR-4312">JCR-4312</a>)</li>
+<li>Check that all subprojects now have the correct version; if not, fix them (for instance, oak-doc and oak-doc-railroad-macro are not in the reactor pom and therefore not updated)</li>
+<li>Send a release announcement to the <a class="externalLink" href="mailto:announce@apache.org,announce@jackrabbit.apache.org,users@jackrabbit.apache.org,dev@jackrabbit.apache.org,oak-dev@jackrabbit.apache.org?subject=%5BANNOUNCE%5D%20Apache%20Jackrabbit%20...%20released">applicable mailing lists</a> once the web site and download mirrors have been synced (template generated in <code>./target/checkout/target/announcement.txt</code> – note that mirrors may need up to 12 hours!). Please note the announce mails needs to be sent from an @apache.org address. In case you are using a mailbox other than apache mailbox (such as gmail) to send mails for your apache address, make sure to send them in plain text format. (Warning: sending the announcement too early may cause it to be rejected for <a class="externalLink" href="mailto:announce@apache.org">announce@apache.org</a>)</li>
</ol></section></section><section>
<h2><a name="Steps_to_build_the_release_artifacts"></a>Steps to build the release artifacts</h2>
<p>The release is built using the Maven release plugin (if your platform is Windows with Cygwin, see <a href="#Appendix_C:_Cygwin">Appendix C</a>). See the <a class="externalLink" href="https://maven.apache.org/developers/release/maven-project-release-procedure.html">Performing a Maven Project Release</a> guide for more details. Make sure you have added the pgp key information in you maven settings file, especially if you have more than one key installed locally. See <a href="#b">Appendix B</a> for the details.</p>
-<p>In case you don't feel comfortable to keep the passwords in the file <code>~/.m2/settings.xml</code> forever, you need to set it now temporarily.</p>
+<p>In case you don’t feel comfortable to keep the passwords in the file <code>~/.m2/settings.xml</code> forever, you need to set it now temporarily.</p>
<p>There have been some problems with certain combinations of Java and Maven versions. A known combinations where releasing was successful is Java 7 with Maven 3.2.2. In case you get an exception “Proxy Error” in the <code>release:perform</code>, see the <a class="externalLink" href="http://status.apache.org/">Apache Services Status Page</a>, however it has been reported that the status page is not always accurate. In case you get an error with respect to API incompatibilities, try with an older Maven version or enforce use of a newer release plugin, such as with <code>mvn org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare</code>.</p>
-<p>Note that preparing the release requires a tagging operation in the source
-repository. Make sure upfront that non-interactive commits work
-(like <code>svn commit -m 'commit message'</code> or <code>git push</code>) without prompting for credentials, otherwise
-the tagging step will fail.</p>
+<p>Note that preparing the release requires a tagging operation in the source repository. Make sure upfront that non-interactive commits work (like <code>svn commit -m 'commit message'</code> or <code>git push</code>) without prompting for credentials, otherwise the tagging step will fail.</p>
<ol style="list-style-type: decimal">
<li>Execute mvn <code>release:prepare</code>. This will update the POM files and tag the release in svn (see <a href="#Appendix_F:_Version_Numbers">Appendix F</a> for how version numbers change).</li>
<li>Execute mvn <code>release:perform</code>. This will build the tagged release and deploy the artifacts to a staging repository on repository.apache.org. The non-Maven release artifacts are automatically deployed to your home directory on people.apache.org. You only need to add the keyname if you have multiple keys and the code signing keys is not your default key.</li>
</ol>
-<p>After this is done, you can remove the passwords from the file <code>~/.m2/settings.xml</code> if you don't want to keep it there.</p></section><section>
+<p>After this is done, you can remove the passwords from the file <code>~/.m2/settings.xml</code> if you don’t want to keep it there.</p></section><section>
<h2><a name="Creating_Markdown_for_Downloads_Page"></a>Creating Markdown for Downloads Page</h2>
-<p>A <a class="externalLink" href="https://dist.apache.org/repos/dist/dev/jackrabbit/create-download-md.sh">shell script</a> is available for generating the downloads links for the mark down source,
-to be run in a checkout of the <a class="externalLink" href="https://dist.apache.org/repos/dist/release/jackrabbit/">release folder</a>.
-Usage:</p>
+<p>A <a class="externalLink" href="https://dist.apache.org/repos/dist/dev/jackrabbit/create-download-md.sh">shell script</a> is available for generating the downloads links for the mark down source, to be run in a checkout of the <a class="externalLink" href="https://dist.apache.org/repos/dist/release/jackrabbit/">release folder</a>. Usage:</p>
+
+<div class="source">
+<div class="source"><pre class="prettyprint linenums"> $ cd path-of-jackrabbit-releases
+</pre></div></div>
-<div class="source"><pre class="prettyprint linenums"><code> $ cd path-of-jackrabbit-releases
-</code></pre></div>
<p>For Jackrabbit:</p>
-<div class="source"><pre class="prettyprint linenums"><code> $ sh create-download-md.sh version
-</code></pre></div>
+<div class="source">
+<div class="source"><pre class="prettyprint linenums"> $ sh create-download-md.sh version
+</pre></div></div>
+
<p>such as:</p>
-<div class="source"><pre class="prettyprint linenums"><code> $ sh create-download-md.sh 2.14.4
-</code></pre></div>
+<div class="source">
+<div class="source"><pre class="prettyprint linenums"> $ sh create-download-md.sh 2.14.4
+</pre></div></div>
+
<p>For Oak:</p>
-<div class="source"><pre class="prettyprint linenums"><code> $ sh create-download-md.sh oak/version
-</code></pre></div>
+<div class="source">
+<div class="source"><pre class="prettyprint linenums"> $ sh create-download-md.sh oak/version
+</pre></div></div>
+
<p>such as:</p>
-<div class="source"><pre class="prettyprint linenums"><code> $ sh create-download-md.sh oak/1.6.6
-</code></pre></div></section><section>
+<div class="source">
+<div class="source"><pre class="prettyprint linenums"> $ sh create-download-md.sh oak/1.6.6
+</pre></div></div>
+</section><section>
<h2><a name="Related_Links"></a>Related Links</h2>
<ul>
@@ -466,43 +353,37 @@ Usage:</p>
<li><a class="externalLink" href="http://www.apache.org/dev/repository-faq.html">http://www.apache.org/dev/repository-faq.html</a></li>
</ul></section><section>
<h2><a name="Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file"></a>Appendix A: Create and add your key to the Jackrabbit KEYS file</h2>
-<p>Follow these instructions to generate your code signing key and to add it
-to the Jackrabbit KEYS file.</p>
+<p>Follow these instructions to generate your code signing key and to add it to the Jackrabbit KEYS file.</p>
<ol style="list-style-type: decimal">
-<li>
+<li><a class="externalLink" href="http://www.apache.org/dev/release-signing.html#generate">Generate a code signing key</a> using your @apache.org address as the email and “CODE SIGNING KEY” as the comment. Also make sure it has been sent to a public key server.</li>
+<li>The Jackrabbit KEYS file is managed in <a class="externalLink" href="https://dist.apache.org/repos/dist/release/jackrabbit/KEYS">https://dist.apache.org/repos/dist/release/jackrabbit/KEYS</a>. To modify the file, first checkout the dist directory:
-<p><a class="externalLink" href="http://www.apache.org/dev/release-signing.html#generate">Generate a code signing key</a>
-using your @apache.org address as the email and “CODE SIGNING KEY” as the comment. Also make sure it has been sent to a public key server.</p>
-</li>
-<li>
-
-<p>The Jackrabbit KEYS file is managed in <a class="externalLink" href="https://dist.apache.org/repos/dist/release/jackrabbit/KEYS">https://dist.apache.org/repos/dist/release/jackrabbit/KEYS</a>. To modify the file, first checkout the dist directory:</p>
-
-<div class="source"><pre class="prettyprint linenums"><code> svn checkout https://dist.apache.org/repos/dist/release/jackrabbit
-</code></pre></div>
+<div class="source">
+<div class="source"><pre class="prettyprint linenums">svn checkout https://dist.apache.org/repos/dist/release/jackrabbit
+</pre></div></div>
</li>
<li>
<p>See <a class="externalLink" href="http://www.apache.org/dev/release-signing.html#keys-policy">instructions on how to append your key to the file</a> (or, as an alternative, the beginning of the KEYS file).</p>
</li>
-<li>
-
-<p>Commit the change using:</p>
+<li>Commit the change using:
-<div class="source"><pre class="prettyprint linenums"><code> svn commit -m "Add code signing key" KEYS
-</code></pre></div>
+<div class="source">
+<div class="source"><pre class="prettyprint linenums">svn commit -m "Add code signing key" KEYS
+</pre></div></div>
</li>
<li>
<p>See the changes on <a class="externalLink" href="http://www.apache.org/dist/jackrabbit/KEYS">http://www.apache.org/dist/jackrabbit/KEYS</a> (you may need to wait a few minutes).</p>
</li>
</ol>
-<p>You can (but don't need to) get your key <a class="externalLink" href="http://www.apache.org/dev/release-signing.html#apache-wot">linked to the Apache web of trust</a>. Once other people have signed your key, you can update the KEYS file with the signatures you've received.</p></section><section>
+<p>You can (but don’t need to) get your key <a class="externalLink" href="http://www.apache.org/dev/release-signing.html#apache-wot">linked to the Apache web of trust</a>. Once other people have signed your key, you can update the KEYS file with the signatures you’ve received.</p></section><section>
<h2><a name="Appendix_B:_Maven_settings"></a>Appendix B: Maven settings</h2>
<p>You need to change the <code>~/.m2/settings.xml</code> file as follows. PGP key id: this is the second part of your key in the KEYS file. For example, this is “F07CA77B” if the first line of your key in the KEYS file is “pub 4096R/F07CA77B 2014-07-31”. In case you are not comfortable to keep passwords and key passphrases in human readable files, you can add them just before doing the release, and remove them just after the release. Instead of using the “gpg.passphrase” tag, you can try using <code><gpg.executable>gpg2</gpg.executable></code> (this should prompt you for the passphrase). For the ASF Maven repository passwords, you could use the <a class="externalLink" href="http://maven.apache.org/guides/mini/guide-encryption.html">Maven password encryption</a>.</p>
-<div class="source"><pre class="prettyprint linenums"><code><settings>
+<div class="source">
+<div class="source"><pre class="prettyprint linenums"><settings>
<profiles>
<profile>
<id>apache-release</id>
@@ -529,21 +410,26 @@ using your @apache.org address as the em
...
</servers>
</settings>
-</code></pre></div></section><section>
+</pre></div></div>
+</section><section>
<h2><a name="Appendix_C:_Cygwin"></a>Appendix C: Cygwin</h2>
-<p>The Subversion and Git support in the release plugin assumes platform-specific path delimiters, and thus does not work properly if the “git” or “svn” executable is the Cygwin version. The easiest workaround for this problem is to install a Windows-native GIT or SVN version as well, and to modify the PATH variable for the git/mvn invocation so that it's found instead of the Cygwin variant.</p></section><section>
+<p>The Subversion and Git support in the release plugin assumes platform-specific path delimiters, and thus does not work properly if the “git” or “svn” executable is the Cygwin version. The easiest workaround for this problem is to install a Windows-native GIT or SVN version as well, and to modify the PATH variable for the git/mvn invocation so that it’s found instead of the Cygwin variant.</p></section><section>
<h2><a name="Appendix_D:_Branching"></a>Appendix D: Branching</h2>
<p>The following notes were collected while branching Jackrabbit 2.16:</p>
<p>Create a JIRA ticket for branching and the subsequent releases of new the branch and trunk; example: <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR-4216">JCR-4216</a>.</p>
<p>Create the branch:</p>
-<div class="source"><pre class="prettyprint linenums"><code>mvn release:branch -DbranchName=2.16 -DdevelopmentVersion=2.17.0-SNAPSHOT
-</code></pre></div>
+<div class="source">
+<div class="source"><pre class="prettyprint linenums">mvn release:branch -DbranchName=2.16 -DdevelopmentVersion=2.17.0-SNAPSHOT
+</pre></div></div>
+
<p>Set the development version on the new branch:</p>
-<div class="source"><pre class="prettyprint linenums"><code>cd path-to-branch-checkout
+<div class="source">
+<div class="source"><pre class="prettyprint linenums">cd path-to-branch-checkout
mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.16.0-SNAPSHOT
-</code></pre></div>
+</pre></div></div>
+
<p>Open a ticket so that once the first release for the branch is made, the <code>comparisonVersion</code> for the <code>bundle:baseline</code> check is updated both in the branch and on trunk; example: <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR-4218">JCR-4218</a>.</p>
<p>Create release notes to include all of the changes accumulated - for 2.16.0 this means including all changes labeled with <code>fixVersion</code> set to <code>2.16</code>. Note that any change labeled with <code>fixVersion</code> set to any 2.15.* release should have <code>fixVersion: 2.16</code> as well, unless the change is irrelevant for the release notes.</p></section><section>
<h2><a name="Appendix_E:_Version_Changes"></a>Appendix E: Version Changes</h2>
@@ -570,28 +456,15 @@ mvn release:update-versions -DautoVersio
<p>Also, check with the “dev” mailing list to confirm that this change is ok.</p></section><section>
<h2><a name="Appendix_F:_Version_Numbers"></a>Appendix F: Version Numbers</h2>
<p><b>Jackrabbit</b></p>
-<p>Classic Jackrabbit uses even minor version numbers for stable releases, and uneven
-numbers for unstable releases. For instance, as of September 2019, the latest
-stable release was “2.18.3”, and the latest unstable release was “2.19.4”.</p>
-<p>Stable releases are cut from a branch, where the branch name is based on
-major and minor version number (here: “2.18”). Unstable releases are built from
-trunk.</p>
-<p>Creating a new major release implies creating a new branch (next would be “2.20”), see
-<a href="#Appendix_D:_Branching">Appendix D</a>.</p>
-<p>For creating releases, the default version numbers proposed by <code>mvn release:prepare</code>
-work out of the box.</p>
+<p>Classic Jackrabbit uses even minor version numbers for stable releases, and uneven numbers for unstable releases. For instance, as of September 2019, the latest stable release was “2.18.3”, and the latest unstable release was “2.19.4”.</p>
+<p>Stable releases are cut from a branch, where the branch name is based on major and minor version number (here: “2.18”). Unstable releases are built from trunk.</p>
+<p>Creating a new major release implies creating a new branch (next would be “2.20”), see <a href="#Appendix_D:_Branching">Appendix D</a>.</p>
+<p>For creating releases, the default version numbers proposed by <code>mvn release:prepare</code> work out of the box.</p>
<p><b>Oak</b></p>
-<p>Oak historically used the same scheme, and moved away from that with “1.10.0” in
-Spring 2019.</p>
-<p>Rather than creating unstable releases from trunk, we now create a stable release
-every time. These keep the even minor numbers, so as of September 2019, the sequence
-of releases since the change was: “1.12.0”, “1.14.0”, “1.16.0”, and “1.18.0”.</p>
-<p>Creating releases from branches continues to work just like for classic Jackrabbit.
-However, when cutting a new stable release from trunk, the default version numbers
-suggested by <code>mvn release:prepare</code> need to be overridden.</p>
-<p>For instance, when cutting “1.20.0”, the next development release will be
-“1.21-SNAPSHOT”, not “1.22-SNAPSHOT”. The following stable release would then
-be “1.22.0”.</p></section>
+<p>Oak historically used the same scheme, and moved away from that with “1.10.0” in Spring 2019.</p>
+<p>Rather than creating unstable releases from trunk, we now create a stable release every time. These keep the even minor numbers, so as of September 2019, the sequence of releases since the change was: “1.12.0”, “1.14.0”, “1.16.0”, and “1.18.0”.</p>
+<p>Creating releases from branches continues to work just like for classic Jackrabbit. However, when cutting a new stable release from trunk, the default version numbers suggested by <code>mvn release:prepare</code> need to be overridden.</p>
+<p>For instance, when cutting “1.20.0”, the next development release will be “1.21-SNAPSHOT”, not “1.22-SNAPSHOT”. The following stable release would then be “1.22.0”.</p></section>
</main>
</div>
</div>
@@ -603,12 +476,10 @@ be “1.22.0”.</p></section>
<a href="https://www.apache.org/">The Apache Software Foundation</a> | <a href="https://privacy.apache.org/policies/privacy-policy-public.html">Privacy Policy</a>
</p>
</div>
- </div>
+ <div id="ohloh" class="pull-right">
+ <script src="https://www.ohloh.net/p/jackrabbit/widgets/project_users_logo.js"></script>
+ </div>
+ </div>
</footer>
-<script>
- if(anchors) {
- anchors.add();
- }
-</script>
</body>
</html>
\ No newline at end of file
Modified: jackrabbit/site/live/jcr/css/apache-maven-fluido-1.11.1.min.css
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/jcr/css/apache-maven-fluido-1.11.1.min.css?rev=1902519&r1=1902518&r2=1902519&view=diff
==============================================================================
--- jackrabbit/site/live/jcr/css/apache-maven-fluido-1.11.1.min.css (original)
+++ jackrabbit/site/live/jcr/css/apache-maven-fluido-1.11.1.min.css Thu Jul 7 09:57:06 2022
@@ -1,20 +1,20 @@
-/*!
- * Bootstrap v2.3.2
- *
- * Copyright 2013 Twitter, Inc
- * Licensed under the Apache License v2.0
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Designed and built with all the love in the world by @mdo and @fat.
[... 33 lines stripped ...]
Added: jackrabbit/site/live/jcr/css/apache-maven-fluido-1.9.min.css
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/jcr/css/apache-maven-fluido-1.9.min.css?rev=1902519&view=auto
==============================================================================
--- jackrabbit/site/live/jcr/css/apache-maven-fluido-1.9.min.css (added)
+++ jackrabbit/site/live/jcr/css/apache-maven-fluido-1.9.min.css Thu Jul 7 09:57:06 2022
@@ -0,0 +1,17 @@
+/*!
+ * Bootstrap v2.3.2
+ *
+ * Copyright 2013 Twitter, Inc
+ * Licensed under the Apache License v2.0
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Designed and built with all the love in the world by @mdo and @fat.
[... 11 lines stripped ...]
Modified: jackrabbit/site/live/jcr/deployment-models.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/jcr/deployment-models.html?rev=1902519&r1=1902518&r2=1902519&view=diff
==============================================================================
--- jackrabbit/site/live/jcr/deployment-models.html (original)
+++ jackrabbit/site/live/jcr/deployment-models.html Thu Jul 7 09:57:06 2022
@@ -1,40 +1,42 @@
<!DOCTYPE html>
-
-
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.11.1 from src/site/markdown/deployment-models.md at 2022-07-05
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from src\site\markdown/deployment-models.md at 2022-05-09
+ | Rendered using Apache Maven Fluido Skin 1.9
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.9.2" />
<title>Apache Jackrabbit – Deployment Models</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.11.1.min.js"></script>
-
- <!-- Matomo -->
- <script>
- var _paq = window._paq = window._paq || [];
- _paq.push(['disableCookies']);
- _paq.push(['trackPageView']);
- _paq.push(['enableLinkTracking']);
-
- (function() {
- var u="https://analytics.apache.org";
- _paq.push(['setTrackerUrl', u+'/matomo.php']);
- _paq.push(['setSiteId', '4']);
- var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
- g.async=true; g.src=u+'/matomo.js'; s.parentNode.insertBefore(g,s);
- })();
- </script>
- <!-- End Matomo Code -->
+ <script src="./js/apache-maven-fluido-1.9.min.js"></script>
+<!-- Matomo -->
+<script>
+ var _paq = window._paq = window._paq || [];
+ /* tracker methods like "setCustomDimension" should be called before "trackPageView" */
+ /* We explicitly disable cookie tracking to avoid privacy issues */
+ _paq.push(['disableCookies']);
+ _paq.push(['trackPageView']);
+ _paq.push(['enableLinkTracking']);
+ (function() {
+ var u="https://matomo.privacy.apache.org/";
+ _paq.push(['setTrackerUrl', u+'matomo.php']);
+ _paq.push(['setSiteId', '4']);
+ var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
+ g.async=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
+ })();
+</script>
+<!-- End Matomo Code -->
</head>
<body class="topBarEnabled">
- <a class="github-fork-ribbon right-top" href="https://github.com/apache/jackrabbit" data-ribbon="Fork me on GitHub" title="Fork me on GitHub">Fork me on GitHub</a>
+ <a href="https://github.com/apache/jackrabbit">
+ <img style="position: absolute; top: 0; right: 0; border: 0; z-index: 10000;"
+ src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"
+ alt="Fork me on GitHub">
+ </a>
<header id="topbar" class="navbar navbar-fixed-top ">
<div class="navbar-inner">
<div class="container-fluid">
@@ -47,7 +49,7 @@
</a>
<ul class="nav">
<li class="dropdown">
- <a class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="index.html" title="Welcome">Welcome</a></li>
<li><a href="downloads.html" title="Downloads">Downloads</a></li>
@@ -58,7 +60,7 @@
</ul>
</li>
<li class="dropdown">
- <a class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="getting-started-with-apache-jackrabbit.html" title="Getting Started">Getting Started</a></li>
<li><a href="standalone-server.html" title="Standalone Server">Standalone Server</a></li>
@@ -66,14 +68,14 @@
<li><a href="first-hops.html" title="First Hops">First Hops</a></li>
<li><a href="jcr-api.html" title="JCR & API">JCR & API</a></li>
<li><a href="jackrabbit-architecture.html" title="Jackrabbit Architecture">Jackrabbit Architecture</a></li>
- <li><a title="Deployment Models">Deployment Models</a></li>
+ <li><a href="deployment-models.html" title="Deployment Models">Deployment Models</a></li>
<li><a href="jackrabbit-configuration.html" title="Jackrabbit Configuration">Jackrabbit Configuration</a></li>
<li><a href="node-types.html" title="Node Types">Node Types</a></li>
<li><a href="object-content-mapping.html" title="Object Content Mapping">Object Content Mapping</a></li>
</ul>
</li>
<li class="dropdown">
- <a class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="jackrabbit-team.html" title="Jackrabbit Team">Jackrabbit Team</a></li>
<li><a href="jackrabbit-roadmap.html" title="Jackrabbit Roadmap">Jackrabbit Roadmap</a></li>
@@ -88,7 +90,7 @@
</ul>
</li>
<li class="dropdown">
- <a class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="https://www.apache.org/foundation/how-it-works.html" title="Introduction">Introduction</a></li>
<li><a href="https://www.apache.org/foundation/sponsorship.html" title="Sponsorship">Sponsorship</a></li>
@@ -103,7 +105,7 @@
<div class="container-fluid">
<header>
<div id="banner">
- <div class="pull-left"><div id="bannerLeft"><h1>Apache Jackrabbit Site</h1>
+ <div class="pull-left"><div id="bannerLeft"><h2>Apache Jackrabbit Site</h2>
</div>
</div>
<div class="pull-right"></div>
@@ -112,7 +114,7 @@
<div id="breadcrumbs">
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2022-07-05</li>
+ <li id="publishDate">Last Published: 2022-05-09</li>
</ul>
</div>
</header>
@@ -134,7 +136,7 @@
<li><a href="first-hops.html" title="First Hops"><span class="none"></span>First Hops</a></li>
<li><a href="jcr-api.html" title="JCR & API"><span class="none"></span>JCR & API</a></li>
<li><a href="jackrabbit-architecture.html" title="Jackrabbit Architecture"><span class="none"></span>Jackrabbit Architecture</a></li>
- <li class="active"><a><span class="none"></span>Deployment Models</a></li>
+ <li class="active"><a href="#"><span class="none"></span>Deployment Models</a></li>
<li><a href="jackrabbit-configuration.html" title="Jackrabbit Configuration"><span class="none"></span>Jackrabbit Configuration</a></li>
<li><a href="node-types.html" title="Node Types"><span class="none"></span>Node Types</a></li>
<li><a href="object-content-mapping.html" title="Object Content Mapping"><span class="none"></span>Object Content Mapping</a></li>
@@ -157,6 +159,7 @@
</ul>
</nav>
<div class="well sidebar-nav">
+ <hr />
<div id="poweredBy">
<div class="clear"></div>
<div class="clear"></div>
@@ -183,14 +186,9 @@
limitations under the License.
-->
<h1>Deployment Models</h1>
-<p>JSR-170 explicitly allows for numerous different deployment models, meaning
-that it is entirely up to the repository implementation to suggest certain
-models.</p>
-<p>Jackrabbit is built to support a variety of different deployment models,
-some of the possibilities on how to deploy Jackrabbit will be outlined
-here.</p>
-<p>See also the following HOWTO documents for setting up and using the
-different deployment models:</p>
+<p>JSR-170 explicitly allows for numerous different deployment models, meaning that it is entirely up to the repository implementation to suggest certain models.</p>
+<p>Jackrabbit is built to support a variety of different deployment models, some of the possibilities on how to deploy Jackrabbit will be outlined here.</p>
+<p>See also the following HOWTO documents for setting up and using the different deployment models:</p>
<ul>
<li><a href="jcr-client-application-howto.html">JCR client application HOWTO</a></li>
@@ -199,69 +197,29 @@ different deployment models:</p>
<li>Model 3: <a href="repository-server-howto.html">Repository Server HOWTO</a></li>
</ul><section>
<h2><a name="Model_1:_The_.28Web-.29_Application_Bundle"></a>Model 1: The (Web-) Application Bundle</h2>
-<p>For many applications, usually applications that run in a closed context
-without interacting with other applications or data sources, it might be
-desirable to bundle a content repository with the application itself.</p>
-<p>Jackrabbit is built for this lightweight model and allows obviously through
-the abstraction provided by JSR-170 to move at any point in time to a
-different deployment model in case this should be desirable for the context
-that the application runs in.</p>
-<p>This makes Jackrabbit ideal to be packaged as a lightweight out-of-the-box
-content repository that allows an application vendor to make sure that
-there are no dependencies to a pre-installed content repository.</p>
-<p>The instance of Jackrabbit that is package with the application is running
-in-proc inside the same JVM and cannot be accessed by any other
-application.</p>
-<p>This deployment model is particularly lightweight and does not require a
-network layer.</p>
-<p>The individual repository instances are started and stopped with their
-containing applications, which means that the application is not only
-connecting to the repository but is also in charge of starting and stopping
-the repository.</p>
-<p>As an example of this deployment model we assume a WebApplication packaged
-into a .war file which is deployed into a WebContainer, which not only
-contains the application but also the actual content repository.</p>
+<p>For many applications, usually applications that run in a closed context without interacting with other applications or data sources, it might be desirable to bundle a content repository with the application itself.</p>
+<p>Jackrabbit is built for this lightweight model and allows obviously through the abstraction provided by JSR-170 to move at any point in time to a different deployment model in case this should be desirable for the context that the application runs in.</p>
+<p>This makes Jackrabbit ideal to be packaged as a lightweight out-of-the-box content repository that allows an application vendor to make sure that there are no dependencies to a pre-installed content repository.</p>
+<p>The instance of Jackrabbit that is package with the application is running in-proc inside the same JVM and cannot be accessed by any other application.</p>
+<p>This deployment model is particularly lightweight and does not require a network layer.</p>
+<p>The individual repository instances are started and stopped with their containing applications, which means that the application is not only connecting to the repository but is also in charge of starting and stopping the repository.</p>
+<p>As an example of this deployment model we assume a WebApplication packaged into a .war file which is deployed into a WebContainer, which not only contains the application but also the actual content repository.</p>
<p><img src="deployment-models-webapp.png" alt="Webapp Deployment" /></p>
-<p>Application1 and Application2 both contain their own instances of a Content
-Repository distributed as a part of their .war file and therefore loaded
-with the web application's class loader which makes it invisible to other
-applications.</p>
-<p>This deployment model of course also works for any stand-alone application
-and not just for web applications.</p></section><section>
+<p>Application1 and Application2 both contain their own instances of a Content Repository distributed as a part of their .war file and therefore loaded with the web application’s class loader which makes it invisible to other applications.</p>
+<p>This deployment model of course also works for any stand-alone application and not just for web applications.</p></section><section>
<h2><a name="Model_2:_Shared_J2EE_Resource"></a>Model 2: Shared J2EE Resource</h2>
-<p>A second way to deploy a repository is to make it visible as a resource to
-all the web applications that are running inside a Servlet Container by
-registering the Repository as a Resource Adapter to the Application Server.</p>
-<p>Similar to the first deployment model this deployment model does also not
-require a network layer and therefore would be considered in-proc and is
-running inside the same JVM.</p>
-<p>The repository is started and stopped with the Application Server but is
-visible to all the applications to connect to.</p>
+<p>A second way to deploy a repository is to make it visible as a resource to all the web applications that are running inside a Servlet Container by registering the Repository as a Resource Adapter to the Application Server.</p>
+<p>Similar to the first deployment model this deployment model does also not require a network layer and therefore would be considered in-proc and is running inside the same JVM.</p>
+<p>The repository is started and stopped with the Application Server but is visible to all the applications to connect to.</p>
<p><img src="deployment-models-j2ee.png" alt="Shared Deployment" /></p>
-<p>This setup also allows to take advantage of the XA facilities of the
-Application Server and could use the application servers single sign-on
-mechanisms that are provided as part of the J2EE framework.</p></section><section>
+<p>This setup also allows to take advantage of the XA facilities of the Application Server and could use the application servers single sign-on mechanisms that are provided as part of the J2EE framework.</p></section><section>
<h2><a name="Model_3:_The_Repository_Server"></a>Model 3: The Repository Server</h2>
-<p>In enterprise environments the client/server deployment model is widely
-used for relational databases. While with relational databases this is
-probably the only deployment model that is supported by most RDBMS vendors
-for repositories, in particular for Jackrabbit, this is only on various
-options.</p>
-<p>The client/server deployment model will certainly be very popular in
-environments that where it is desirable to physically separate the content
-repository (or data) layer from the application or presentation layer, so
-the content repository can be used from many different applications,
-physically and can be scaled individually.</p>
+<p>In enterprise environments the client/server deployment model is widely used for relational databases. While with relational databases this is probably the only deployment model that is supported by most RDBMS vendors for repositories, in particular for Jackrabbit, this is only on various options.</p>
+<p>The client/server deployment model will certainly be very popular in environments that where it is desirable to physically separate the content repository (or data) layer from the application or presentation layer, so the content repository can be used from many different applications, physically and can be scaled individually.</p>
<p><img src="deployment-models-server.png" alt="Standalone Deployment" /></p>
-<p>This deployment model assumes that there is a network layer between the
-content repository server and the respective content repository client.</p>
-<p>While the applications communicate through the JSR-170 API with the content
-repository client. The content repository client then communicates through
-any form of transport protocol with the stand-alone content repository
-server.</p>
-<p>The transport protocol between the client and the server is subject to
-implementation and not mandated by JSR-170. Popular choices might include
-RMI over JRMP or IIOP or WebDAV and its extensions.</p></section>
+<p>This deployment model assumes that there is a network layer between the content repository server and the respective content repository client.</p>
+<p>While the applications communicate through the JSR-170 API with the content repository client. The content repository client then communicates through any form of transport protocol with the stand-alone content repository server.</p>
+<p>The transport protocol between the client and the server is subject to implementation and not mandated by JSR-170. Popular choices might include RMI over JRMP or IIOP or WebDAV and its extensions.</p></section>
</main>
</div>
</div>
@@ -273,12 +231,10 @@ RMI over JRMP or IIOP or WebDAV and its
<a href="https://www.apache.org/">The Apache Software Foundation</a> | <a href="https://privacy.apache.org/policies/privacy-policy-public.html">Privacy Policy</a>
</p>
</div>
- </div>
+ <div id="ohloh" class="pull-right">
+ <script src="https://www.ohloh.net/p/jackrabbit/widgets/project_users_logo.js"></script>
+ </div>
+ </div>
</footer>
-<script>
- if(anchors) {
- anchors.add();
- }
-</script>
</body>
</html>
\ No newline at end of file
Modified: jackrabbit/site/live/jcr/documentation.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/jcr/documentation.html?rev=1902519&r1=1902518&r2=1902519&view=diff
==============================================================================
--- jackrabbit/site/live/jcr/documentation.html (original)
+++ jackrabbit/site/live/jcr/documentation.html Thu Jul 7 09:57:06 2022
@@ -1,40 +1,42 @@
<!DOCTYPE html>
-
-
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.11.1 from src/site/markdown/documentation.md at 2022-07-05
- | Rendered using Apache Maven Fluido Skin 1.11.1
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from src\site\markdown/documentation.md at 2022-05-09
+ | Rendered using Apache Maven Fluido Skin 1.9
-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.9.2" />
<title>Apache Jackrabbit – Documentation</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.11.1.min.js"></script>
-
- <!-- Matomo -->
- <script>
- var _paq = window._paq = window._paq || [];
- _paq.push(['disableCookies']);
- _paq.push(['trackPageView']);
- _paq.push(['enableLinkTracking']);
-
- (function() {
- var u="https://analytics.apache.org";
- _paq.push(['setTrackerUrl', u+'/matomo.php']);
- _paq.push(['setSiteId', '4']);
- var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
- g.async=true; g.src=u+'/matomo.js'; s.parentNode.insertBefore(g,s);
- })();
- </script>
- <!-- End Matomo Code -->
+ <script src="./js/apache-maven-fluido-1.9.min.js"></script>
+<!-- Matomo -->
+<script>
+ var _paq = window._paq = window._paq || [];
+ /* tracker methods like "setCustomDimension" should be called before "trackPageView" */
+ /* We explicitly disable cookie tracking to avoid privacy issues */
+ _paq.push(['disableCookies']);
+ _paq.push(['trackPageView']);
+ _paq.push(['enableLinkTracking']);
+ (function() {
+ var u="https://matomo.privacy.apache.org/";
+ _paq.push(['setTrackerUrl', u+'matomo.php']);
+ _paq.push(['setSiteId', '4']);
+ var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
+ g.async=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
+ })();
+</script>
+<!-- End Matomo Code -->
</head>
<body class="topBarEnabled">
- <a class="github-fork-ribbon right-top" href="https://github.com/apache/jackrabbit" data-ribbon="Fork me on GitHub" title="Fork me on GitHub">Fork me on GitHub</a>
+ <a href="https://github.com/apache/jackrabbit">
+ <img style="position: absolute; top: 0; right: 0; border: 0; z-index: 10000;"
+ src="https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa0000.png"
+ alt="Fork me on GitHub">
+ </a>
<header id="topbar" class="navbar navbar-fixed-top ">
<div class="navbar-inner">
<div class="container-fluid">
@@ -47,7 +49,7 @@
</a>
<ul class="nav">
<li class="dropdown">
- <a class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Jackrabbit <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="index.html" title="Welcome">Welcome</a></li>
<li><a href="downloads.html" title="Downloads">Downloads</a></li>
@@ -58,7 +60,7 @@
</ul>
</li>
<li class="dropdown">
- <a class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="getting-started-with-apache-jackrabbit.html" title="Getting Started">Getting Started</a></li>
<li><a href="standalone-server.html" title="Standalone Server">Standalone Server</a></li>
@@ -73,7 +75,7 @@
</ul>
</li>
<li class="dropdown">
- <a class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Development <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="jackrabbit-team.html" title="Jackrabbit Team">Jackrabbit Team</a></li>
<li><a href="jackrabbit-roadmap.html" title="Jackrabbit Roadmap">Jackrabbit Roadmap</a></li>
@@ -88,7 +90,7 @@
</ul>
</li>
<li class="dropdown">
- <a class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Apache Software Foundation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="https://www.apache.org/foundation/how-it-works.html" title="Introduction">Introduction</a></li>
<li><a href="https://www.apache.org/foundation/sponsorship.html" title="Sponsorship">Sponsorship</a></li>
@@ -103,7 +105,7 @@
<div class="container-fluid">
<header>
<div id="banner">
- <div class="pull-left"><div id="bannerLeft"><h1>Apache Jackrabbit Site</h1>
+ <div class="pull-left"><div id="bannerLeft"><h2>Apache Jackrabbit Site</h2>
</div>
</div>
<div class="pull-right"></div>
@@ -112,7 +114,7 @@
<div id="breadcrumbs">
<ul class="breadcrumb">
- <li id="publishDate">Last Published: 2022-07-05</li>
+ <li id="publishDate">Last Published: 2022-05-09</li>
</ul>
</div>
</header>
@@ -157,6 +159,7 @@
</ul>
</nav>
<div class="well sidebar-nav">
+ <hr />
<div id="poweredBy">
<div class="clear"></div>
<div class="clear"></div>
@@ -206,12 +209,10 @@
<a href="https://www.apache.org/">The Apache Software Foundation</a> | <a href="https://privacy.apache.org/policies/privacy-policy-public.html">Privacy Policy</a>
</p>
</div>
- </div>
+ <div id="ohloh" class="pull-right">
+ <script src="https://www.ohloh.net/p/jackrabbit/widgets/project_users_logo.js"></script>
+ </div>
+ </div>
</footer>
-<script>
- if(anchors) {
- anchors.add();
- }
-</script>
</body>
</html>
\ No newline at end of file