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 mb...@apache.org on 2022/02/04 22:39:16 UTC
[db-jdo-site] branch 3.2 updated: Update link references from link:.html to xref:.adoc
This is an automated email from the ASF dual-hosted git repository.
mbo pushed a commit to branch 3.2
in repository https://gitbox.apache.org/repos/asf/db-jdo-site.git
The following commit(s) were added to refs/heads/3.2 by this push:
new 2bb9875 Update link references from link:<name>.html to xref:<name>.adoc
2bb9875 is described below
commit 2bb987568f9b81ebd4ccf1251f8cf261f78e634a
Author: Michael Bouschen <Mi...@akquinet.de>
AuthorDate: Fri Feb 4 23:39:00 2022 +0100
Update link references from link:<name>.html to xref:<name>.adoc
---
src/main/asciidoc/annotations.adoc | 18 +++++++++---------
src/main/asciidoc/attach_detach.adoc | 8 ++++----
src/main/asciidoc/fetchgroups.adoc | 2 +-
src/main/asciidoc/get-involved.adoc | 6 +++---
src/main/asciidoc/getting-started.adoc | 2 +-
src/main/asciidoc/impls.adoc | 2 +-
src/main/asciidoc/index.adoc | 18 +++++++++---------
src/main/asciidoc/jdo_dtd.adoc | 2 +-
src/main/asciidoc/jdo_v_jpa.adoc | 2 +-
src/main/asciidoc/orm_dtd.adoc | 2 +-
src/main/asciidoc/pm.adoc | 6 +++---
src/main/asciidoc/pmf.adoc | 2 +-
src/main/asciidoc/release-3.0.1.adoc | 4 ++--
src/main/asciidoc/release-3.1-rc1.adoc | 4 ++--
src/main/asciidoc/state_transition.adoc | 2 +-
src/main/asciidoc/tck.adoc | 2 +-
src/main/asciidoc/team-list.adoc | 4 ++--
src/main/asciidoc/transactions.adoc | 2 +-
18 files changed, 44 insertions(+), 44 deletions(-)
diff --git a/src/main/asciidoc/annotations.adoc b/src/main/asciidoc/annotations.adoc
index 47cfe7f..a0be091 100644
--- a/src/main/asciidoc/annotations.adoc
+++ b/src/main/asciidoc/annotations.adoc
@@ -237,7 +237,7 @@ public class MyClass
}
....
-See the documentation for link:class_types.html[Class Types]
+See the documentation for xref:class_types.adoc[Class Types]
{empty} +
@@ -439,7 +439,7 @@ public class MyClass
}
....
-See the documentation for link:transactions.html[transactions]
+See the documentation for xref:transactions.adoc[transactions]
{empty} +
@@ -502,7 +502,7 @@ public class MyClass
}
....
-See the documentation for link:fetchgroups.html[FetchGroups]
+See the documentation for xref:fetchgroups.adoc[FetchGroups]
{empty} +
@@ -538,7 +538,7 @@ public class MyClass
}
....
-See the documentation for link:fetchgroups.html[FetchGroups]
+See the documentation for xref:fetchgroups.adoc[FetchGroups]
{empty} +
@@ -577,7 +577,7 @@ public class MyClass
}
....
-See the documentation for link:fetchgroups.html[FetchGroups]
+See the documentation for xref:fetchgroups.adoc[FetchGroups]
{empty} +
@@ -617,7 +617,7 @@ public class MyClass
}
....
-See the documentation for link:fetchgroups.html[FetchGroups]
+See the documentation for xref:fetchgroups.adoc[FetchGroups]
{empty} +
@@ -1147,7 +1147,7 @@ public class MyClass
}
....
-See the documentation for link:field_types.html[Field Types]
+See the documentation for xref:field_types.adoc[Field Types]
{empty} +
@@ -1196,7 +1196,7 @@ public class MyClass
}
....
-See the documentation for link:field_types.html[Field Types]
+See the documentation for xref:field_types.adoc[Field Types]
{empty} +
@@ -1222,7 +1222,7 @@ public class MyClass
}
....
-See the documentation for link:field_types.html[Field Types]
+See the documentation for xref:field_types.adoc[Field Types]
{empty} +
diff --git a/src/main/asciidoc/attach_detach.adoc b/src/main/asciidoc/attach_detach.adoc
index ae911e2..84504af 100644
--- a/src/main/asciidoc/attach_detach.adoc
+++ b/src/main/asciidoc/attach_detach.adoc
@@ -14,7 +14,7 @@ fields manually and copy them back to the persisted object later. JDO
2.0 introduces a new way of handling this situation, by *detaching* an
object from the persistence graph, allowing it to be worked on in the
users application. It can then be *attached* to the persistence graph
-later. Please refer to link:state_transition.html[Object Lifecycle] for
+later. Please refer to xref:state_transition.adoc[Object Lifecycle] for
where this fits in. The first thing to do to use a class with this
facility is to tag it as "detachable". This is done by adding the
attribute
@@ -23,7 +23,7 @@ attribute
<class name="MyClass" detachable="true">
....
-This acts as an instruction to the link:enhancement.html[enhancement
+This acts as an instruction to the xref:enhancement.adoc[enhancement
process] to add methods necessary to utilise the attach/detach process.
The following code fragment highlights how to use the attach/detach
@@ -100,11 +100,11 @@ them later (updating the associated object in the datastore. If you want
to create copies of the objects in the datastore with their own
identities you should use _makeTransient_ instead of _detachCopy_.
* Calling _detachCopy_ will detach all fields of that object that are in
-the current link:fetchgroups.html[Fetch Group] for that class for that
+the current xref:fetchgroups.adoc[Fetch Group] for that class for that
_PersistenceManager_.
* By default the fields of the object that will be detached are those in
the _Default Fetch Group_.
-* You should choose your link:fetchgroups.html[Fetch Group] carefully,
+* You should choose your xref:fetchgroups.adoc[Fetch Group] carefully,
bearing in mind which object(s) you want to access whilst detached.
Detaching a relation field will detach the related object as well.
* If you don't detach a field of an object, you [.underline]#cannot#
diff --git a/src/main/asciidoc/fetchgroups.adoc b/src/main/asciidoc/fetchgroups.adoc
index 29147f6..e96ffd2 100644
--- a/src/main/asciidoc/fetchgroups.adoc
+++ b/src/main/asciidoc/fetchgroups.adoc
@@ -161,7 +161,7 @@ _PersistenceManager.newQuery()_, _PersistenceManager.getExtent()_,
_PersistenceManager.detachCopy_ and much more besides.
You can read more about *named fetch-groups* and how to use it with
-link:attach_detach.html[*attach/detach*]
+xref:attach_detach.adoc[*attach/detach*]
anchor:dynamic[]
diff --git a/src/main/asciidoc/get-involved.adoc b/src/main/asciidoc/get-involved.adoc
index a92002f..2eeedb2 100644
--- a/src/main/asciidoc/get-involved.adoc
+++ b/src/main/asciidoc/get-involved.adoc
@@ -22,7 +22,7 @@ If a pull request is related to an existing https://issues.apache.org/jira/secur
This will automatically create a reference to the pull request in the ticket.
Please also include a link to the referenced JIRA ticket in the pull request message.
-More information on how to access the project source code is available link:source-code.html[here].
+More information on how to access the project source code is available xref:source-code.adoc[here].
=== Reporting Bugs
@@ -34,12 +34,12 @@ Bugs and other issues can be posted on the project https://issues.apache.org/jir
The project uses different channels of communication:
-* Discussion occurs on the link:mail-lists.html[JDO mailing lists].
+* Discussion occurs on the xref:mail-lists.adoc[JDO mailing lists].
* Additional documentation and discussion can be found on the project http://wiki.apache.org/jdo/[wiki].
* We have a communications conference call every week.
During this call we discuss project status, issues, concerns, and strategy.
Everyone interested in Apache JDO is welcome and encouraged to participate.
- The agenda is available on the Dev List (see link:mail-lists.html[JDO mailing lists]).
+ The agenda is available on the Dev List (see xref:mail-lists.adoc[JDO mailing lists]).
=== Contributing as a Non-Committer
diff --git a/src/main/asciidoc/getting-started.adoc b/src/main/asciidoc/getting-started.adoc
index 36aebc4..5199ced 100644
--- a/src/main/asciidoc/getting-started.adoc
+++ b/src/main/asciidoc/getting-started.adoc
@@ -28,7 +28,7 @@ using the JDO implementation classes to define the application view of
PersistenceManagerFactory and PersistenceManager.
Next, choose a JDO implementation. You can get information
-on JDO implementations link:impls.html[here]. Some factors to consider when choosing
+on JDO implementations xref:impls.adoc[here]. Some factors to consider when choosing
a JDO implementation is what databases they support, what Java version
they support, and whether they provide tools to create database schema from
an object model or create an object model from the database schema.
diff --git a/src/main/asciidoc/impls.adoc b/src/main/asciidoc/impls.adoc
index cc3dcdb..3f05bb2 100644
--- a/src/main/asciidoc/impls.adoc
+++ b/src/main/asciidoc/impls.adoc
@@ -10,7 +10,7 @@
To build and run your JDO application, you need a JDO implementation.
This page lists commercial and non-commercial JDO implementations. For
information on how vendors certify compliance with the JDO
-specifications, see link:tck.html[TCK].
+specifications, see xref:tck.adoc[TCK].
=== JDO Reference Implementationsanchor:JDO_Reference_Implementations[]
diff --git a/src/main/asciidoc/index.adoc b/src/main/asciidoc/index.adoc
index 355df5d..5b34321 100644
--- a/src/main/asciidoc/index.adoc
+++ b/src/main/asciidoc/index.adoc
@@ -42,7 +42,7 @@ The Apache JDO project is focused on building the JDO API and the TCK
for compatibility testing of JDO implementations. Commercial and open
source implementations of JDO are available for relational databases,
object databases, and file systems. If you need an implementation for
-building a JDO application, see link:impls.html[Implementations].
+building a JDO application, see xref:impls.adoc[Implementations].
== JDO Newsanchor:JDO_News[]
@@ -91,7 +91,7 @@ JDO 3.0.1 has been released. This release contains minor bug fixes. For
a complete list of changes (features plus bug fixes) see
https://issues.apache.org/jira/browse/JDO/fixforversion/12317950[JDO
3.0.1 changes]. You can download the release from the
-link:downloads.html[downloads page]. You can also use the new release in
+xref:downloads.adoc[downloads page]. You can also use the new release in
maven projects simply by referencing the jdo-api artifact in your
pom.xml.
____
@@ -106,7 +106,7 @@ cancel, and exact object ids. For a complete list of changes (features
plus bug fixes) see
https://issues.apache.org/jira/browse/JDO/fixforversion/12313404[JDO 3.0
changes]. You can download the release from the
-link:downloads.html[downloads page]. You can also use the new release in
+xref:downloads.adoc[downloads page]. You can also use the new release in
maven projects simply by referencing the jdo-api artifact in your
pom.xml.
____
@@ -115,7 +115,7 @@ ____
____
JDO 2.2 is now available for download from the
-link:downloads.html[downloads page]. The JDO 2.2 maintenance release
+xref:downloads.adoc[downloads page]. The JDO 2.2 maintenance release
provides support for copyOnAttach control, dynamic fetch groups, level2
caching control via metadata. For details, see
http://jcp.org/aboutJava/communityprocess/maintenance/jsr243/243MR2.html[ChangeLog
@@ -126,14 +126,14 @@ ____
____
JDO 2.1.1 is now available for download from the
-link:downloads.html[downloads page]. This is a minor bug fix release.
+xref:downloads.adoc[downloads page]. This is a minor bug fix release.
____
*JDO 2.1 is released* +
____
JDO 2.1 is now available for download from the
-link:downloads.html[downloads page]. The JDO 2.1 maintenance release
+xref:downloads.adoc[downloads page]. The JDO 2.1 maintenance release
provides support for JDK 1.5 features,including the use of annotations
as a means of specifying mapping. It also includes many corrections and
minor changes. For details, see
@@ -145,7 +145,7 @@ ____
____
JDO 2.0 is now available for download from the
-link:downloads.html[downloads page]. JDO 2.0 builds on JDO 1 and
+xref:downloads.adoc[downloads page]. JDO 2.0 builds on JDO 1 and
includes many features requested by users:
* Standard mapping from objects to relational databases
@@ -170,7 +170,7 @@ the JDO standard.
We'd love to have you involved. Check out the
http://wiki.apache.org/jdo[Wiki]. Check out the
http://www.jcp.org/en/jsr/detail?id=243[Specification], which has been
-approved. link:./get-involved.html[Get Involved]!
+approved. xref:./get-involved.adoc[Get Involved]!
-_Archived articles are link:newshistory.html[here]_.
+_Archived articles are xref:newshistory.adoc[here]_.
diff --git a/src/main/asciidoc/jdo_dtd.adoc b/src/main/asciidoc/jdo_dtd.adoc
index 5c4f27c..955a73a 100644
--- a/src/main/asciidoc/jdo_dtd.adoc
+++ b/src/main/asciidoc/jdo_dtd.adoc
@@ -12,7 +12,7 @@
JDO defines XML MetaData in *jdo* files as well as *orm* files. As
always with XML, the metadata must match the defined DTD/XSD for that
file type. This section describes the content of the *jdo* files. The
-content of *orm* files can be found link:orm_dtd.html[here]. All *jdo*
+content of *orm* files can be found xref:orm_dtd.adoc[here]. All *jdo*
files must contain a valid DTD/DOCTYPE specification. You can use PUBLIC
or SYSTEM versions of these.
diff --git a/src/main/asciidoc/jdo_v_jpa.adoc b/src/main/asciidoc/jdo_v_jpa.adoc
index 8591275..a03eee9 100644
--- a/src/main/asciidoc/jdo_v_jpa.adoc
+++ b/src/main/asciidoc/jdo_v_jpa.adoc
@@ -110,7 +110,7 @@ columns, *FK constraints*, *index columns*, *index constraints*, unique
key columns, *unique key constraints* |Tables, columns, PK columns, FK
columns, unique key columns
-|ORM Relationships |link:jdo_v_jpa_orm.html[*Full range of Collection,
+|ORM Relationships |xref:jdo_v_jpa_orm.adoc[*Full range of Collection,
Map, List, Array, 1-1, 1-N, M-N using PC, Non-PC and interface objects*]
|Basic 1-1, 1-N, M-N, Collection<NonPC>, Map<NonPC>
diff --git a/src/main/asciidoc/orm_dtd.adoc b/src/main/asciidoc/orm_dtd.adoc
index 6d2d6f3..6451014 100644
--- a/src/main/asciidoc/orm_dtd.adoc
+++ b/src/main/asciidoc/orm_dtd.adoc
@@ -12,7 +12,7 @@
JDO defines XML MetaData in *jdo* files as well as *orm* files. As
always with XML, the metadata must match the defined DTD/XSD for that
file type. This section describes the content of the *orm* files. The
-content of *jdo* files can be found link:jdo_dtd.html[here]. All *orm*
+content of *jdo* files can be found xref:jdo_dtd.adoc[here]. All *orm*
files must contain a valid DTD/DOCTYPE specification. You can use PUBLIC
or SYSTEM versions of these.
diff --git a/src/main/asciidoc/pm.adoc b/src/main/asciidoc/pm.adoc
index f350f42..5ff84a9 100644
--- a/src/main/asciidoc/pm.adoc
+++ b/src/main/asciidoc/pm.adoc
@@ -9,7 +9,7 @@
Any JDO-enabled application will require at least one
_PersistenceManager_ (PM). This is obtained from the
-link:pmf.html[PersistenceManagerFactory] for the datastore.
+xref:pmf.adoc[PersistenceManagerFactory] for the datastore.
The simplest way of creating a _PersistenceManager_
link:api20/apidocs/javax/jdo/PersistenceManager.html[image:images/javadoc.png[image]]
@@ -30,7 +30,7 @@ datastore. A _PersistenceManager_ has a single transaction.
=== Persist Objectsanchor:Persist_Objects[]
To persist an object, the object must first be marked as persistable
-using link:metadata.html[MetaData (XML/Annotations)]. Then you would
+using xref:metadata.adoc[MetaData (XML/Annotations)]. Then you would
start the PM transaction, and use _makePersistent_ as follows
....
@@ -193,7 +193,7 @@ catch (Exception e)
=== Making an object transientanchor:Making_an_object_transient[]
-As we have seen in the link:state_transition.html[JDO States guide], an
+As we have seen in the xref:state_transition.adoc[JDO States guide], an
object can have many possible states. When we want to take an object and
work on it, but removing its identity we can make it *transient*. This
means that it will retain the values of its fields, yet will no longer
diff --git a/src/main/asciidoc/pmf.adoc b/src/main/asciidoc/pmf.adoc
index 29850e7..8537a3a 100644
--- a/src/main/asciidoc/pmf.adoc
+++ b/src/main/asciidoc/pmf.adoc
@@ -117,7 +117,7 @@ Range of Values: true \| false
|*javax.jdo.option.Optimistic*
-|Whether to use link:transactions.html[Optimistic transactions]. Range of Values: true \| false
+|Whether to use xref:transactions.html[Optimistic transactions]. Range of Values: true \| false
|*javax.jdo.option.RetainValues*
diff --git a/src/main/asciidoc/release-3.0.1.adoc b/src/main/asciidoc/release-3.0.1.adoc
index b57c39a..fae6680 100644
--- a/src/main/asciidoc/release-3.0.1.adoc
+++ b/src/main/asciidoc/release-3.0.1.adoc
@@ -8,8 +8,8 @@
== 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 link:downloads.html[Downloads].
-For information on running the TCK, see link:tck.html[TCK].
+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.
diff --git a/src/main/asciidoc/release-3.1-rc1.adoc b/src/main/asciidoc/release-3.1-rc1.adoc
index 46583f8..73b3a7d 100644
--- a/src/main/asciidoc/release-3.1-rc1.adoc
+++ b/src/main/asciidoc/release-3.1-rc1.adoc
@@ -8,8 +8,8 @@
== 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 link:downloads.html[Downloads].
-For information on running the TCK, see link:tck.html[TCK].
+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.
diff --git a/src/main/asciidoc/state_transition.adoc b/src/main/asciidoc/state_transition.adoc
index 99b0dac..415838a 100644
--- a/src/main/asciidoc/state_transition.adoc
+++ b/src/main/asciidoc/state_transition.adoc
@@ -65,7 +65,7 @@ instance whose values have been changed since detaching.
=== Detecting Object Stateanchor:Detecting_Object_State[]
-JDO provides a class link:jdohelper.html[JDOHelper] that allows you to
+JDO provides a class xref:jdohelper.adoc[JDOHelper] that allows you to
interrogate the object state via its attributes (isPersistent(),
isDeleted(), etc). In JDO 2.1 for JDKs 1.5+ _JDOHelper_ is extended to
also provide a method that gives the full object state.
diff --git a/src/main/asciidoc/tck.adoc b/src/main/asciidoc/tck.adoc
index 1f31658..6b21ee8 100644
--- a/src/main/asciidoc/tck.adoc
+++ b/src/main/asciidoc/tck.adoc
@@ -19,7 +19,7 @@ To run the Technology Compatibility Kit:
[arabic]
. Check out the JDO source code from the most recent branch. See
-link:source-code.html[Source Code] for instructions on
+xref:source-code.adoc[Source Code] for instructions on
checking out code.
. Follow the instructions in the Prerequisites section of
https://github.com/apache/db-jdo/blob/main/README.md[README.md]
diff --git a/src/main/asciidoc/team-list.adoc b/src/main/asciidoc/team-list.adoc
index ea1a635..db692f0 100644
--- a/src/main/asciidoc/team-list.adoc
+++ b/src/main/asciidoc/team-list.adoc
@@ -12,12 +12,12 @@ working long and hard to make quality software for the rest of the world
to use.
If you would like to contribute to JDO, please see the
-link:roadmap.html[roadmap] list to find areas where you can contribute.
+xref:roadmap.adoc[roadmap] list to find areas where you can contribute.
If there is nothing in there that suits your interest, but you still
have ideas, please feel free to suggest them on the mailing list.
If you would like to become a committer, please see
-link:get-involved.html[Get Involved].
+xref:get-involved.adoc[Get Involved].
=== Apache JDO Committersanchor:Apache_JDO_Committers[]
diff --git a/src/main/asciidoc/transactions.adoc b/src/main/asciidoc/transactions.adoc
index 71b8b3c..e6b5335 100644
--- a/src/main/asciidoc/transactions.adoc
+++ b/src/main/asciidoc/transactions.adoc
@@ -10,7 +10,7 @@
== Transactionsanchor:Transactions[]
When managing the persistence of objects using a
-link:pm.html[PersistenceManager] it is normal to handle all datastore
+xref:pm.adoc[PersistenceManager] it is normal to handle all datastore
operations in a transaction. For this reason each _PersistenceManager_
has its own transaction. Consequently a typical JDO persistence method
will look something like this