You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-commits@db.apache.org by ti...@apache.org on 2022/05/04 19:30:06 UTC
[db-jdo-site] branch main updated: JDO-805 Replace download pages
This is an automated email from the ASF dual-hosted git repository.
tilmannz pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/db-jdo-site.git
The following commit(s) were added to refs/heads/main by this push:
new 991607b JDO-805 Replace download pages
991607b is described below
commit 991607bf59a042c47e3265b928eee893ee068266
Author: Tilmann <zo...@gmx.de>
AuthorDate: Wed May 4 21:29:58 2022 +0200
JDO-805 Replace download pages
---
src/main/asciidoc/downloads-all.adoc | 113 -------------------------------
src/main/asciidoc/downloads.adoc | 110 ++++++++++++++++++++++++------
src/main/asciidoc/release-3.0.1.adoc | 119 ---------------------------------
src/main/asciidoc/release-3.1-rc1.adoc | 98 ---------------------------
src/main/asciidoc/release-3.1.adoc | 101 ----------------------------
src/main/asciidoc/release-3.2.adoc | 95 --------------------------
6 files changed, 91 insertions(+), 545 deletions(-)
diff --git a/src/main/asciidoc/downloads-all.adoc b/src/main/asciidoc/downloads-all.adoc
deleted file mode 100644
index bf4ebb6..0000000
--- a/src/main/asciidoc/downloads-all.adoc
+++ /dev/null
@@ -1,113 +0,0 @@
-:_basedir:
-:_imagesdir: images/
-:grid: cols
-:development:
-
-[[index]]
-
-== Downloadsanchor:Downloads[]
-
-To develop your own code to use or implement JDO, you can use the links below to download Apache JDO from an
-official ASF download site. If you are using Maven, you can declare a dependency using the instructions below.
-
-If you intend to develop JDO (make modifications to the JDO code), you should clone the
-xref:source-code.adoc[public repository] and submit pull requests if desired.
-
-Please see instruction below for xref:Verifying[verifying the integrity] of the
-distribution files after downloading any artifacts.
-
-
-=== Maven (convenience binary)anchor:Maven[]
-
-The most convenient way to use JDO is to configure your project using Maven.
-The JDO API can be downloaded
-automatically by maven and placed into your local maven repository if you
-include the proper dependency in your maven project definition.
-For example:
-[source,xml]
-<dependency>
- <groupId>javax.jdo</groupId>
- <artifactId>jdo-api</artifactId>
- <version>3.2</version>
-</dependency>
-
-=== Source Downloads
-
-[cols="18%,12%,20%,15%,20%,15%",options="header"]
-|===
-|Release Notes | Date | Sources .tar.gz | asc / sha | Sources .zip | asc / sha
-| https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12316653&styleName=Html&projectId=10630[3.2]
-| 2022-02-01
-| https://www.apache.org/dyn/closer.lua/db/jdo/3.2/jdo-3.2-source-release.tar.gz[src.tar.gz (1.1 MB)]
-| https://downloads.apache.org/db/jdo/3.2/jdo-3.2-source-release.tar.gz.asc[asc] /
- https://downloads.apache.org/db/jdo/3.2/jdo-3.2-source-release.tar.gz.sha512[sha512]
-| https://www.apache.org/dyn/closer.lua/db/jdo/3.2/jdo-3.2-source-release.zip[src.zip (2.8 MB)]
-| https://downloads.apache.org/db/jdo/3.2/jdo-3.2-source-release.zip.asc[asc] /
- https://downloads.apache.org/db/jdo/3.2/jdo-3.2-source-release.zip.sha512[sha512]
-
-| https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12325878&styleName=Html&projectId=10630[3.1]
-| 2015-03-20
-| https://www.apache.org/dyn/closer.lua/db/jdo/3.1/jdo-3.1-src.tar.gz[src.tar.gz (1.1 MB)]
-| https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.tar.gz.asc[asc] /
-https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.tar.gz.sha1[sha1]
-| https://www.apache.org/dyn/closer.lua/db/jdo/3.1/jdo-3.1-src.zip[src.zip (2.8 MB)]
-| https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.zip.asc[asc] /
-https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.zip.sha1[sha1]
-
-| https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317950&styleName=Html&projectId=10630[3.0.1] TCK
-| 2011-11-13
-| https://www.apache.org/dyn/closer.lua/db/jdo/3.0.1/jdo-tck-3.0.1-src.zip[tck-src.zip]
-| https://downloads.apache.org/db/jdo/3.0.1/jdo-tck-3.0.1-src.zip.asc[asc]
-| https://www.apache.org/dyn/closer.lua/db/jdo/3.0.1/jdo-tck-3.0.1-src.tar.gz[tck-src.tar.gz]
-| https://downloads.apache.org/db/jdo/3.0.1/jdo-tck-3.0.1-src.tar.gz.asc[asc]
-
-| https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317950&styleName=Html&projectId=10630[3.0.1] API
-| 2011-11-13
-| https://www.apache.org/dyn/closer.lua/db/jdo/3.0.1/jdo-api-3.0.1-src.zip[api-src.zip]
-| https://downloads.apache.org/db/jdo/3.0.1/jdo-api-3.0.1-src.zip.asc[asc]
-| https://www.apache.org/dyn/closer.lua/db/jdo/3.0.1/jdo-api-3.0.1-src.tar.gz[api-src.tar.gz]
-| https://downloads.apache.org/db/jdo/3.0.1/jdo-api-3.0.1-src.tar.gz.asc[asc]
-|===
-
-
-=== About JDO Releasesanchor:About_JDO_Releases[]
-
-A release of JDO includes the JDO API and the Technology Compatibility
-Kit (TCK). The TCK is available only in source form. The API project is
-available as source and as a jar file using the standard Maven dependency protocol.
-
-* The `jdo-api.jar` file is the only artifact needed for users who wish to compile their programs
-using the JDO API. It can be downloaded from maven, or it can be built
-manually from the source code.
-* The TCK project contains the JDO Technology Compatibility Kit.
-
-The 3.0.1 release has separate downloads for API and TCK sources. Newer distributions have all code in
-in a single download.
-
-
-=== Verifying Releasesanchor:Verifying_Releases[]
-
-anchor:Verifying[]
-
-It is essential that you verify the integrity of the downloaded files
-using the PGP signature.
-
-The PGP signatures can be verified using PGP or GPG. First download the
-link:https://downloads.apache.org/db/jdo/KEYS[KEYS] as well as the `asc`
-signature file for the particular distribution. Make sure you get these
-files from the link:https://downloads.apache.org/db/jdo/[Apache downbload area], rather than from a mirror. Then verify the signatures using
-these commands (depending on your tool set):
-
-[source]
-% pgpk -a KEYS
-% pgpv release_artifact.asc
-
-[source]
-% pgp -ka KEYS
-% pgp release_artifact.asc
-
-[source]
-% gpg --import KEYS
-% gpg --verify release_artifact.asc
-
-
diff --git a/src/main/asciidoc/downloads.adoc b/src/main/asciidoc/downloads.adoc
index a652f71..2195e30 100644
--- a/src/main/asciidoc/downloads.adoc
+++ b/src/main/asciidoc/downloads.adoc
@@ -1,4 +1,4 @@
-:_basedir:
+:_basedir:
:_imagesdir: images/
:grid: cols
:development:
@@ -7,19 +7,68 @@
== Downloadsanchor:Downloads[]
-=== Latest Official Releaseanchor:Latest_Official_Release[]
+To develop your own code to use or implement JDO, you can use the links below to download Apache JDO from an
+official ASF download site. If you are using Maven, you can declare a dependency using the instructions below.
-<<release-3.2.adoc#,JDO 3.2>> image:images/dot_clear.png[image]
-February 1, 2022
+If you intend to develop JDO (make modifications to the JDO code), you should clone the
+xref:source-code.adoc[public repository] and submit pull requests if desired.
-=== Previous Official Releasesanchor:Previous_Official_Releases[]
+Please see instruction below for xref:Verifying[verifying the integrity] of the
+distribution files after downloading any artifacts.
-<<release-3.1.adoc#,JDO 3.1>> image:images/dot_clear.png[image]
-March 20, 2015
-<<release-3.1-rc1.adoc#,JDO 3.1-rc1>> image:images/dot_clear.png[image] September 22, 2013
+=== Maven (convenience binary)anchor:Maven[]
+
+The most convenient way to use JDO is to configure your project using Maven.
+The JDO API can be downloaded
+automatically by maven and placed into your local maven repository if you
+include the proper dependency in your maven project definition.
+For example:
+[source,xml]
+<dependency>
+ <groupId>javax.jdo</groupId>
+ <artifactId>jdo-api</artifactId>
+ <version>3.2</version>
+</dependency>
+
+=== Source Downloads
+
+[cols="18%,12%,20%,15%,20%,15%",options="header"]
+|===
+|Release Notes | Date | Sources .tar.gz | asc / sha | Sources .zip | asc / sha
+| https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12316653&styleName=Html&projectId=10630[3.2]
+| 2022-02-01
+| https://www.apache.org/dyn/closer.lua/db/jdo/3.2/jdo-3.2-source-release.tar.gz[src.tar.gz (1.1 MB)]
+| https://downloads.apache.org/db/jdo/3.2/jdo-3.2-source-release.tar.gz.asc[asc] /
+https://downloads.apache.org/db/jdo/3.2/jdo-3.2-source-release.tar.gz.sha512[sha512]
+| https://www.apache.org/dyn/closer.lua/db/jdo/3.2/jdo-3.2-source-release.zip[src.zip (2.8 MB)]
+| https://downloads.apache.org/db/jdo/3.2/jdo-3.2-source-release.zip.asc[asc] /
+https://downloads.apache.org/db/jdo/3.2/jdo-3.2-source-release.zip.sha512[sha512]
+
+| https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12325878&styleName=Html&projectId=10630[3.1]
+| 2015-03-20
+| https://www.apache.org/dyn/closer.lua/db/jdo/3.1/jdo-3.1-src.tar.gz[src.tar.gz (1.1 MB)]
+| https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.tar.gz.asc[asc] /
+https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.tar.gz.sha1[sha1]
+| https://www.apache.org/dyn/closer.lua/db/jdo/3.1/jdo-3.1-src.zip[src.zip (2.8 MB)]
+| https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.zip.asc[asc] /
+https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.zip.sha1[sha1]
+
+| https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317950&styleName=Html&projectId=10630[3.0.1] TCK
+| 2011-11-13
+| https://www.apache.org/dyn/closer.lua/db/jdo/3.0.1/jdo-tck-3.0.1-src.zip[tck-src.zip]
+| https://downloads.apache.org/db/jdo/3.0.1/jdo-tck-3.0.1-src.zip.asc[asc]
+| https://www.apache.org/dyn/closer.lua/db/jdo/3.0.1/jdo-tck-3.0.1-src.tar.gz[tck-src.tar.gz]
+| https://downloads.apache.org/db/jdo/3.0.1/jdo-tck-3.0.1-src.tar.gz.asc[asc]
+
+| https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317950&styleName=Html&projectId=10630[3.0.1] API
+| 2011-11-13
+| https://www.apache.org/dyn/closer.lua/db/jdo/3.0.1/jdo-api-3.0.1-src.zip[api-src.zip]
+| https://downloads.apache.org/db/jdo/3.0.1/jdo-api-3.0.1-src.zip.asc[asc]
+| https://www.apache.org/dyn/closer.lua/db/jdo/3.0.1/jdo-api-3.0.1-src.tar.gz[api-src.tar.gz]
+| https://downloads.apache.org/db/jdo/3.0.1/jdo-api-3.0.1-src.tar.gz.asc[asc]
+|===
-<<release-3.0.1.adoc#,JDO 3.0.1>> image:images/dot_clear.png[image] November 13, 2011
=== About JDO Releasesanchor:About_JDO_Releases[]
@@ -27,13 +76,36 @@ A release of JDO includes the JDO API and the Technology Compatibility
Kit (TCK). The TCK is available only in source form. The API project is
available as source and as a jar file using the standard Maven dependency protocol.
-* The source release contains sources to build jdo-api.jar. The jar file is
-the only artifact needed for users who wish to compile their programs
-using the JDO API. It can be downloaded automatically by maven and
-placed into the local maven repository if you include the proper
-dependency in your maven project definition. Use groupId javax.jdo,
-artifactId jdo-ap and version 3.2. Alternatively, it can be downloaded
-manually from Maven and put into a location of your choice.
-* The tck project contains the JDO Technology Compatibility Kit. The
-source distribution is the only artifact needed to be downloaded by the
-user.
+* The `jdo-api.jar` file is the only artifact needed for users who wish to compile their programs
+using the JDO API. It can be downloaded from maven, or it can be built
+manually from the source code.
+* The TCK project contains the JDO Technology Compatibility Kit.
+
+The 3.0.1 release has separate downloads for API and TCK sources. Newer distributions have all code in
+in a single download.
+
+
+=== Verifying Releasesanchor:Verifying_Releases[]
+
+anchor:Verifying[]
+
+It is essential that you verify the integrity of the downloaded files
+using the PGP signature.
+
+The PGP signatures can be verified using PGP or GPG. First download the
+link:https://downloads.apache.org/db/jdo/KEYS[KEYS] as well as the `asc`
+signature file for the particular distribution. Make sure you get these
+files from the link:https://downloads.apache.org/db/jdo/[Apache downbload area], rather than from a mirror. Then verify the signatures using
+these commands (depending on your tool set):
+
+[source]
+% pgpk -a KEYS
+% pgpv release_artifact.asc
+
+[source]
+% pgp -ka KEYS
+% pgp release_artifact.asc
+
+[source]
+% gpg --import KEYS
+% gpg --verify release_artifact.asc
diff --git a/src/main/asciidoc/release-3.0.1.adoc b/src/main/asciidoc/release-3.0.1.adoc
deleted file mode 100644
index fae6680..0000000
--- a/src/main/asciidoc/release-3.0.1.adoc
+++ /dev/null
@@ -1,119 +0,0 @@
-:_basedir:
-:_imagesdir: images/
-:grid: cols
-:development:
-
-[[index]]
-
-== JDO 3.0.1 Distributionsanchor:JDO_3.0.1_Distributions[]
-
-Use the links below to download Apache JDO from one of our mirrors. For
-more information about the projects see xref:downloads.adoc[Downloads].
-For information on running the TCK, see xref:tck.adoc[TCK].
-
-It is good practice to xref:Verifying[verify the integrity] of the
-distribution files.
-
-You are currently using *http://apache.mirrors.nublue.co.uk/*. If you
-encounter a problem with this mirror, then please select another. If all
-mirrors are failing, there are backup mirrors at the end of the list.
-See http://www.apache.org/mirrors/[status] of mirrors.
-
-Other mirrors:
-
-* http://apache.mirror.anlx.net/
-* http://apache.mirrors.nublue.co.uk/
-* http://mirror.ox.ac.uk/sites/rsync.apache.org/
-* http://mirror.vorboss.net/apache/
-* http://mirrors.ukfast.co.uk/sites/ftp.apache.org/
-* http://www.mirrorservice.org/sites/ftp.apache.org/
-* ftp://ftp.mirrorservice.org/sites/ftp.apache.org/
-* https://www-eu.apache.org/dist/ (backup)
-* https://www-us.apache.org/dist/ (backup)
-
-
-{empty} +
-
-
-=== Release Notesanchor:Release_Notes[]
-
-https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317950&styleName=Html&projectId=10630[View
-release notes for JDO 3.0.1]
-
-=== APIanchor:API[]
-
-The api project contains source to build jdo-api.jar, which defines the
-JDO API. The jar file is the only artifact needed for users who wish to
-compile their programs using the JDO API. It can be downloaded
-automatically by maven and placed into the local maven repository if you
-include the proper dependency in your maven project definition. Use
-groupId javax.jdo, artifactId jdo-api, version 3.0 and define your
-remote repository as http://www.ibiblio.org/maven. Alternatively, it can
-be downloaded manually and put into a location of your choice.
-
-* http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/jars/jdo-api-3.0.1.jar[jdo-api-3.0.1.jar]
-http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/jars/jdo-api-3.0.1.jar.asc[PGP]
-http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/jars/jdo-api-3.0.1.jar.md5[MD5]
-
-* http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/poms/jdo-api-3.0.1.pom[jdo-api-3.0.1.pom]
-http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/poms/jdo-api-3.0.1.pom.asc[PGP]
-http://people.apache.org/repo/m1-ibiblio-rsync-repository/javax.jdo/poms/jdo-api-3.0.1.pom.md5[MD5]
-
-* http://apache.mirrors.nublue.co.uk//db/jdo/3.0.1/jdo-api-3.0.1-src.zip[jdo-api-3.0.1-src.zip]
-http://www.apache.org/dist/db/jdo/3.0.1/jdo-api-3.0.1-src.zip.asc[PGP]
-http://www.apache.org/dist/db/jdo/3.0.1/jdo-api-3.0.1-src.zip.md5[MD5]
-
-* http://apache.mirrors.nublue.co.uk//db/jdo/3.0.1/jdo-api-3.0.1-src.tar.gz[jdo-api-3.0.1-src.tar.gz]
-http://www.apache.org/dist/db/jdo/3.0.1/jdo-api-3.0.1-src.tar.gz.asc[PGP]
-http://www.apache.org/dist/db/jdo/3.0.1/jdo-api-3.0.1-src.tar.gz.md5[MD5]
-
-=== TCKanchor:TCK[]
-
-This is a download for all implementors of JDO, and for those who want
-to check how well an implementation is compliant with the JDO
-specification. The tck2 project contains the JDO 2 Technology
-Compatibility Kit. The source distribution is the only artifact needed
-to be downloaded by the user. The dependencies (including the model20
-jar, util20 jar, enhancer20 jar, api2 jar, and JPOX) are automatically
-downloaded by maven as needed to run the TCK.
-
-* http://apache.mirrors.nublue.co.uk//db/jdo/3.0.1/jdo-tck-3.0.1-src.zip[jdo-tck-3.0.1-src.zip]
-http://www.apache.org/dist/db/jdo/3.0.1/jdo-tck-3.0.1-src.zip.asc[PGP]
-http://www.apache.org/dist/db/jdo/3.0.1/jdo-tck-3.0.1-src.zip.md5[MD5]
-
-* http://apache.mirrors.nublue.co.uk//db/jdo/3.0.1/jdo-tck-3.0.1-src.tar.gz[jdo-tck-3.0.1-src.tar.gz]
-http://www.apache.org/dist/db/jdo/3.0.1/jdo-tck-3.0.1-src.tar.gz.asc[PGP]
-http://www.apache.org/dist/db/jdo/3.0.1/jdo-tck-3.0.1-src.tar.gz.md5[MD5]
-
-== Verifying Releasesanchor:Verifying_Releases[]
-
-anchor:Verifying[]
-
-It is essential that you verify the integrity of the downloaded files
-using the PGP signature and/or the MD5 checksum. The checksum is not as
-strong an indicator as the PGP signature is.
-
-The PGP signatures can be verified using PGP or GPG. First download the
-http://www.apache.org/dist/db/jdo/KEYS[KEYS] as well as the `asc`
-signature file for the particular distribution. Make sure you get these
-files from the http://www.apache.org/dist/db/jdo/[main distribution
-directory], rather than from a mirror. Then verify the signatures using
-
-` % pgpk -a KEYS % pgpv release_name.tar.gz.asc` _or_ +
-` % pgp -ka KEYS % pgp release_name.tar.gz.asc` _or_ +
-` % gpg --import KEYS % gpg --verify release_name.tar.gz.asc`
-
-Alternatively, you can verify the checksums on the files. Unix programs
-called `md5`/`sha1` or `md5sum`/`sha1sum` are included in many unix
-distributions. `*sum` is also available as part of
-http://www.gnu.org/software/textutils/textutils.html[GNU Textutils].
-Windows users can get binary md5 programs from
-http://www.fourmilab.ch/md5/[http://www.fourmilab.ch/md5] and
-http://www.pc-tools.net/win32/freeware/console/[hhttp://www.pc-tools.net/win32/freeware/console].
-Windows SlavaSoft http://www.slavasoft.com/fsum/[fsum] supports MD5 and
-SHA1.
-
-We highly recommend verifying the PGP signature, though.
-
-'''''
-
diff --git a/src/main/asciidoc/release-3.1-rc1.adoc b/src/main/asciidoc/release-3.1-rc1.adoc
deleted file mode 100644
index 73b3a7d..0000000
--- a/src/main/asciidoc/release-3.1-rc1.adoc
+++ /dev/null
@@ -1,98 +0,0 @@
-:_basedir:
-:_imagesdir: images/
-:grid: cols
-:development:
-
-[[index]]
-
-== JDO 3.1-rc1 Distributionsanchor:JDO_3.1-rc1_Distributions[]
-
-Use the links below to download Apache JDO from one of our mirrors. For
-more information about the projects see xref:downloads.adoc[Downloads].
-For information on running the TCK, see xref:tck.adoc[TCK].
-
-It is good practice to xref:Verifying[verify the integrity] of the
-distribution files.
-
-You are currently using
-*http://mirror.ox.ac.uk/sites/rsync.apache.org/*. If you encounter a
-problem with this mirror, then please select another. If all mirrors are
-failing, there are backup mirrors at the end of the list. See
-http://www.apache.org/mirrors/[status] of mirrors.
-
-Other mirrors:
-
-* http://apache.mirror.anlx.net/
-* http://apache.mirrors.nublue.co.uk/
-* http://mirror.ox.ac.uk/sites/rsync.apache.org/
-* http://mirror.vorboss.net/apache/
-* http://mirrors.ukfast.co.uk/sites/ftp.apache.org/
-* http://www.mirrorservice.org/sites/ftp.apache.org/
-* ftp://ftp.mirrorservice.org/sites/ftp.apache.org/
-* https://www-eu.apache.org/dist/ (backup)
-* https://www-us.apache.org/dist/ (backup)
-
-
-{empty} +
-
-
-=== Release Notesanchor:Release_Notes[]
-
-https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12314921&styleName=Html&projectId=10630[View
-release notes for JDO 3.1-rc1]
-
-=== APIanchor:API[]
-
-The api project contains source to build jdo-api.jar, which defines the
-JDO API. The jar file is the only artifact needed for users who wish to
-compile their programs using the JDO API. It can be downloaded
-automatically by maven and placed into the local maven repository if you
-include the proper dependency in your maven project definition. Use
-groupId javax.jdo, artifactId jdo-api, version 3.1-rc1 and define your
-remote repository as http://www.ibiblio.org/maven. Alternatively, it can
-be downloaded manually and put into a location of your choice.
-
-* http://mirror.ox.ac.uk/sites/rsync.apache.org//db/jdo/3.1-rc1/jdo-api-3.1-rc1.jar[jdo-api-3.1-rc1.jar]
-http://www.apache.org/dist/db/jdo/3.1-rc1/jdo-api-3.1-rc1.jar.asc[PGP]
-
-* http://mirror.ox.ac.uk/sites/rsync.apache.org//db/jdo/3.1-rc1/jdo-api-3.1-rc1.pom[jdo-api-3.1-rc1.pom]
-http://www.apache.org/dist/db/jdo/3.1-rc1/jdo-api-3.1-rc1.pom.asc[PGP]
-
-* http://mirror.ox.ac.uk/sites/rsync.apache.org//db/jdo/3.1-rc1/jdo-api-3.1-rc1-sources.jar[jdo-api-3.1-rc1-sources.jar]
-http://www.apache.org/dist/db/jdo/3.1-rc1/jdo-api-3.1-rc1-sources.jar.asc[PGP]
-
-=== TCKanchor:TCK[]
-
-This is a download for all implementors of JDO, and for those who want
-to check how well an implementation is compliant with the JDO
-specification. The tck project contains the JDO Technology Compatibility
-Kit. The source distribution is the only artifact needed to be
-downloaded by the user. The dependencies are automatically downloaded by
-maven as needed to run the TCK. Please refer to the README.html for
-further details.
-
-* http://mirror.ox.ac.uk/sites/rsync.apache.org//db/jdo/3.1-rc1/jdo-3.1-rc1-src.zip[jdo-3.1-rc1-src.zip]
-http://www.apache.org/dist/db/jdo/3.1-rc1/jdo-3.1-rc1-src.zip.asc[PGP]
-
-* http://mirror.ox.ac.uk/sites/rsync.apache.org//db/jdo/3.1-rc1/jdo-3.1-rc1-src.tar.gz[jdo-3.1-rc1-src.tar.gz]
-http://www.apache.org/dist/db/jdo/3.1-rc1/jdo-3.1-rc1-src.tar.gz.asc[PGP]
-
-== Verifying Releasesanchor:Verifying_Releases[]
-
-anchor:Verifying[]
-
-It is essential that you verify the integrity of the downloaded files
-using the PGP signature.
-
-The PGP signatures can be verified using PGP or GPG. First download the
-http://www.apache.org/dist/db/jdo/KEYS[KEYS] as well as the `asc`
-signature file for the particular distribution. Make sure you get these
-files from the http://www.apache.org/dist/db/jdo/[main distribution
-directory], rather than from a mirror. Then verify the signatures using
-
-` % pgpk -a KEYS % pgpv release_name.tar.gz.asc` _or_ +
-` % pgp -ka KEYS % pgp release_name.tar.gz.asc` _or_ +
-` % gpg --import KEYS % gpg --verify release_name.tar.gz.asc`
-
-'''''
-
diff --git a/src/main/asciidoc/release-3.1.adoc b/src/main/asciidoc/release-3.1.adoc
deleted file mode 100644
index 9b091e4..0000000
--- a/src/main/asciidoc/release-3.1.adoc
+++ /dev/null
@@ -1,101 +0,0 @@
-:_basedir:
-:_imagesdir: images/
-:grid: cols
-:development:
-
-[[index]]
-
-== JDO 3.1 Distributionsanchor:JDO_3.1_Distributions[]
-
-If you intend to develop JDO (make modifications to the JDO code), you should
-clone the public repository and submit pull requests if desired.
-You can use this url: https://github.com/apache/db-jdo.git[db-jdo.git]
-
-To develop your own code to use JDO, you can use the links below
-to download Apache JDO from one of the official ASF mirrors.
-If you are using Maven, you can declare a dependency using the instructions below.
-
-It is essential to xref:Verifying[verify the integrity] of the
-distribution files after downloading any artifacts.
-
-=== Release Notesanchor:Release_Notes[]
-
-https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12325878&styleName=Html&projectId=10630[View
-release notes for JDO 3.1]
-
-=== APIanchor:API[]
-
-The api project contains source to build jdo-api.jar, which defines the
-JDO API. The jar file is the only artifact needed for users who wish to
-compile their programs using the JDO API.
-
-https://www.apache.org/dyn/closer.lua/db/jdo/3.1/jdo-api-3.1-sources.jar[jdo-api-3.1-sources.jar]
-https://downloads.apache.org/db/jdo/3.1/jdo-api-3.1-sources.jar.asc[asc]
-https://downloads.apache.org/db/jdo/3.1/jdo-api-3.1-sources.jar.sha1[sha1]
-https://downloads.apache.org/db/jdo/3.1/jdo-api-3.1-sources.jar.md5[md5]
-
-==== Maven (convenience binary)anchor:Maven[]
-
-The JDO API can be downloaded
-automatically by maven and placed into the local maven repository if you
-include the proper dependency in your maven project definition.
-For example:
-[source,xml]
-<dependency>
- <groupId>javax.jdo</groupId>
- <artifactId>jdo-api</artifactId>
- <version>3.1</version>
-</dependency>
-
-=== TCKanchor:TCK[]
-
-This is a download for all implementors of JDO, and for those who want
-to check how well an implementation is compliant with the JDO
-specification.
-
-The TCK project contains the JDO Technology Compatibility
-Kit. The source distribution is the only artifact needed to be
-downloaded by the user and contains all of the sources used to build
-the JDO project including the API, TCK, and test artifacts.
-The dependencies are automatically downloaded by
-maven as needed to run the TCK.
-
-Please refer to the README for further details.
-
-https://www.apache.org/dyn/closer.lua/db/jdo/3.1/jdo-3.1-src.tar.gz[jdo-3.1-src.tar.gz (1.1 MB)]
-https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.tar.gz.asc[asc]
-https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.tar.gz.sha1[sha1]
-https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.tar.gz.md5[md5]
-
-https://www.apache.org/dyn/closer.lua/db/jdo/3.1/jdo-3.1-src.zip[jdo-3.1-src.zip (2.8 MB)]
-https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.zip.asc[asc]
-https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.zip.sha1[sha1]
-https://downloads.apache.org/db/jdo/3.1/jdo-3.1-src.zip.md5[md5]
-
-=== Verifying Releasesanchor:Verifying_Releases[]
-
-anchor:Verifying[]
-
-It is essential that you verify the integrity of the downloaded files
-using the PGP signature.
-
-The PGP signatures can be verified using PGP or GPG. First download the
-link:https://www.apache.org/dist/db/jdo/KEYS[KEYS] as well as the `asc`
-signature file for the particular distribution. Make sure you get these
-files from the link:https://www.apache.org/dist/db/jdo/[main distribution
-directory], rather than from a mirror. Then verify the signatures using
-these commands (depending on your tool set):
-
-[source]
-% pgpk -a KEYS
-% pgpv release_artifact.asc
-
-[source]
-% pgp -ka KEYS
-% pgp release_artifact.asc
-
-[source]
-% gpg --import KEYS
-% gpg --verify release_artifact.asc
-
-
diff --git a/src/main/asciidoc/release-3.2.adoc b/src/main/asciidoc/release-3.2.adoc
deleted file mode 100644
index bc04306..0000000
--- a/src/main/asciidoc/release-3.2.adoc
+++ /dev/null
@@ -1,95 +0,0 @@
-:_basedir:
-:_imagesdir: images/
-:grid: cols
-:development:
-
-[[index]]
-
-== JDO 3.2 Distributionsanchor:JDO_3.2_Distributions[]
-
-To develop your own code to use or implement JDO, you can use the links below
-to download Apache JDO from an official ASF download site.
-If you are using Maven, you can declare a dependency using the instructions below.
-
-=== Source releaseanchor:Source_Release[]
-
-The full source release is available for download. This includes the API and TCK.
-
-It is essential to xref:Verifying[verify the integrity] of the
-distribution files after downloading any artifacts.
-
-https://www.apache.org/dyn/closer.lua/db/jdo/3.2/jdo-3.2-source-release.tar.gz[jdo-3.2-source-release.tar.gz (1.1 MB)]
-https://downloads.apache.org/db/jdo/3.2/jdo-3.2-source-release.tar.gz.asc[asc]
-https://downloads.apache.org/db/jdo/3.2/jdo-3.2-source-release.tar.gz.sha512[sha512]
-
-https://www.apache.org/dyn/closer.lua/db/jdo/3.2/jdo-3.2-source-release.zip[jdo-3.2-source-release.zip (2.8 MB)]
-https://downloads.apache.org/db/jdo/3.2/jdo-3.2-source-release.zip.asc[asc]
-https://downloads.apache.org/db/jdo/3.2/jdo-3.2-source-release.zip.sha512[sha512]
-
-==== Release Notesanchor:Release_Notes[]
-
-https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12316653&styleName=Html&projectId=10630[View
-release notes for JDO 3.2]
-
-=== Maven (convenience binary)anchor:Maven[]
-
-The most convenient way to use JDO is to configure your project using Maven.
-The JDO API can be downloaded
-automatically by maven and placed into your local maven repository if you
-include the proper dependency in your maven project definition.
-For example:
-[source,xml]
-<dependency>
- <groupId>javax.jdo</groupId>
- <artifactId>jdo-api</artifactId>
- <version>3.2</version>
-</dependency>
-
-=== Developers of the JDO project
-
-If you develop JDO (make modifications to the JDO code), you can
-clone the public git repository and submit pull requests if desired.
-You can use this url: https://github.com/apache/db-jdo.git[db-jdo.git]
-
-=== TCKanchor:TCK[]
-
-The TCK is intended for all implementors of JDO, and for those who want
-to check whether an implementation is compliant with the JDO
-specification. It is included in the full xref:Source_Release[source release].
-
-The TCK project contains the JDO Technology Compatibility
-Kit. The source distribution is the only artifact needed to be
-downloaded by the user and contains all of the sources used to build
-the JDO project including the API, TCK, and test artifacts.
-The dependencies are automatically downloaded by
-maven as needed to run the TCK.
-
-Please refer to the README for further details.
-
-=== Verifying Releasesanchor:Verifying_Releases[]
-
-anchor:Verifying[]
-
-It is essential that you verify the integrity of the downloaded files
-using the PGP signature.
-
-The PGP signatures can be verified using PGP or GPG. First download the
-link:https://downloads.apache.org/db/jdo/KEYS[KEYS] as well as the `asc`
-signature file for the particular distribution. Make sure you get these
-files from the link:https://downloads.apache.org/db/jdo/[main distribution
-directory]. Then verify the signatures using
-these commands (depending on your tool set):
-
-[source]
-% pgpk -a KEYS
-% pgpv release_artifact.asc
-
-[source]
-% pgp -ka KEYS
-% pgp release_artifact.asc
-
-[source]
-% gpg --import KEYS
-% gpg --verify release_artifact.asc
-
-