fix broken links due to change in how APT parses the links
git-svn-id: https://svn.apache.org/repos/asf/maven/ant-tasks/trunk@1091699 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/src/site/apt/index.apt b/src/site/apt/index.apt
index 0e33886..41a9998 100644
--- a/src/site/apt/index.apt
+++ b/src/site/apt/index.apt
@@ -38,7 +38,7 @@
* <POM processing> - for reading and writing a Maven 2 <<<pom.xml>>> file
- The Ant tasks can be downloaded from the {{{download.html} download page}}.
+ The Ant tasks can be downloaded from the {{{./download.html} download page}}.
* System Requirements
@@ -51,7 +51,7 @@
* Usage
General instructions for installing and using the Maven Ant Tasks can be found on the
- {{{installation.html}installation page}} and the {{{usage.html}usage page}} respectively.
+ {{{./installation.html}installation page}} and the {{{./usage.html}usage page}} respectively.
Some more specific use cases are described in the examples given below. Last but not least,
users occasionally contribute additional examples, tips or errata to the
{{{http://docs.codehaus.org/display/MAVENUSER/Maven+Ant+Tasks}project's wiki page}}.
@@ -60,29 +60,29 @@
Several common usage examples are provided for the following tasks:
- * {{{examples/dependencies.html}Dependencies task}}
+ * {{{./examples/dependencies.html}Dependencies task}}
- * {{{examples/install-deploy.html}Install and Deploy tasks}}
+ * {{{./examples/install-deploy.html}Install and Deploy tasks}}
- * {{{examples/pom.html}Pom task}}
+ * {{{./examples/pom.html}Pom task}}
- * {{{examples/write-pom.html}WritePom task}}
+ * {{{./examples/write-pom.html}WritePom task}}
- * {{{examples/mvn.html}Mvn task}}
+ * {{{./examples/mvn.html}Mvn task}}
* Getting Help
- In case you still have questions regarding the Maven Ant Tasks usage, please have a look at the {{{faq.html}FAQ}} and feel
- free to contact the {{{mail-lists.html}user mailing list}}. The posts to the mailing list are archived and could
+ In case you still have questions regarding the Maven Ant Tasks usage, please have a look at the {{{./faq.html}FAQ}} and feel
+ free to contact the {{{./mail-lists.html}user mailing list}}. The posts to the mailing list are archived and could
already contain the answer to your question as part of an older thread. Hence, it is also worth browsing/searching
- the {{{mail-lists.html}mail archive}}.
+ the {{{./mail-lists.html}mail archive}}.
If you feel like the Ant tasks are missing a feature or have a defect, you can fill a feature request or bug report in our
- {{{issue-tracking.html}issue tracker}}. When creating a new issue, please provide a comprehensive description of your
+ {{{./issue-tracking.html}issue tracker}}. When creating a new issue, please provide a comprehensive description of your
concern. Especially for fixing bugs it is crucial that the developers can reproduce your problem. For this reason,
entire debug logs, Ant build scripts or most preferably little demo projects attached to the issue are very much appreciated.
Of course, patches are welcome, too. Contributors can check out the project from our
- {{{source-repository.html}source repository}} and will find supplementary information in the
+ {{{./source-repository.html}source repository}} and will find supplementary information in the
{{{http://maven.apache.org/guides/development/guide-helping.html}guide to helping with Maven}}.
For more information on the Maven functionality behind the Ant tasks, try the following links:
diff --git a/src/site/apt/installation.apt.vm b/src/site/apt/installation.apt.vm
index 0b1bc6b..4e9e4da 100644
--- a/src/site/apt/installation.apt.vm
+++ b/src/site/apt/installation.apt.vm
@@ -30,7 +30,7 @@
Installing Maven Ant Tasks
For convenience, Maven Ant Tasks and all its dependencies are packaged together as a single JAR file.
- This can be downloaded from the {{{download.html} download page}}.
+ This can be downloaded from the {{{./download.html} download page}}.
There are two ways to use the tasks from your scripts.
diff --git a/src/site/apt/reference.apt b/src/site/apt/reference.apt
index 39fe330..e5bc5c0 100644
--- a/src/site/apt/reference.apt
+++ b/src/site/apt/reference.apt
@@ -62,7 +62,7 @@
*-------------------------+---------------------------------------------------------------------------+--------------+-------------+
| <<<scopes>>> | A comma separated list of specific scopes to be retrieved. If no value is provided, all scopes will be included. | No | 2.0.10 |
*-------------------------+---------------------------------------------------------------------------+--------------+-------------+
-| <<<versionsId>>> | The property ID to store the versions of the resolved dependencies, for use by a {{{reference.html#VersionMapper} <<<VersionMapper>>>}}. | No | 2.0.7 |
+| <<<versionsId>>> | The property ID to store the versions of the resolved dependencies, for use by a {{{./reference.html#VersionMapper} <<<VersionMapper>>>}}. | No | 2.0.7 |
*-------------------------+---------------------------------------------------------------------------+--------------+-------------+
| <<<cacheDependencyRefs>>> | If set to true, will generate an Ant build file that contains properties and fileset references for the dependencies. Then try to load information from this file in subsequent builds. Default is <false>. | No | 2.1.0 |
*-------------------------+---------------------------------------------------------------------------+--------------+-------------+
@@ -72,15 +72,15 @@
*-------------------------+---------------------------------------------------------------------------+--------------+-------------+
The task can include the <<<dependency>>> nested type, in addition to the other shared types
- {{{reference.html#localRepository} <<<localRepository>>>}}, {{{reference.html#pom} <<<pom>>>}} and
- {{{reference.html#remoteRepository} <<<remoteRepository>>>}}, which will be explained later.
+ {{{./reference.html#localRepository} <<<localRepository>>>}}, {{{./reference.html#pom} <<<pom>>>}} and
+ {{{./reference.html#remoteRepository} <<<remoteRepository>>>}}, which will be explained later.
You must include either
a single <<<pom>>> element
or a <<<pomRefId>>> attribute
or one or more <<<dependency>>> elements.
- If you have set a value for <<<versionsId>>>, you can later use {{{reference.html#versionMapper} <<<VersionMapper>>>}}.
+ If you have set a value for <<<versionsId>>>, you can later use {{{./reference.html#versionMapper} <<<VersionMapper>>>}}.
<(since 2.0.8)> For each dependency resolved, the property <<<groupId:artifactId:type[:classifier]>>> is defined pointing to
the corresponding file.
@@ -146,10 +146,10 @@
| <<<uniqueVersion>>> | (<<<deploy>>> only) Whether to assign snapshots a unique version comprised of the timestamp and build number, or to use the same version each time | No, the default is <<<true>>>. | |
*---------------------+--------------------------------------------------------------------------+-------------------------------------------------+-------------+
- The task must take either a nested {{{reference.html#pom} <<<pom>>>}} element, or a <<<pomRefId>>> attribute. Both release and <<<-SNAPSHOT>>> versions are supported.
- The task can have an optional {{{reference.html#localRepository} <<<localRepository>>>}} nested element.
+ The task must take either a nested {{{./reference.html#pom} <<<pom>>>}} element, or a <<<pomRefId>>> attribute. Both release and <<<-SNAPSHOT>>> versions are supported.
+ The task can have an optional {{{./reference.html#localRepository} <<<localRepository>>>}} nested element.
- <<<deploy>>> can have an optional {{{reference.html#remoteRepository} <<<remoteRepository>>>}} nested element. If no
+ <<<deploy>>> can have an optional {{{./reference.html#remoteRepository} <<<remoteRepository>>>}} nested element. If no
<<<remoteRepository>>> nested element is given, the <<<distributionManagement>>> section of the POM is used.
** <<<attach>>> <(since 2.0.6)>
@@ -323,5 +323,5 @@
| <<<to>>> | If this is set to <<<flatten>>> the directory info is also removed from the filename. | No |
*------------------+--------------------------------------------------------+--------------+
- You can see a full working example in the {{{examples/dependencies.html} examples}}.
+ You can see a full working example in the {{{./examples/dependencies.html} examples}}.
diff --git a/src/site/apt/usage.apt b/src/site/apt/usage.apt
index 8ed076d..d570ca4 100644
--- a/src/site/apt/usage.apt
+++ b/src/site/apt/usage.apt
@@ -51,10 +51,10 @@
You may have noticed the <<<pathId>>> reference. This is optional, but if given will create a classpath reference
that includes the local files downloaded as dependencies. This is usually used to pass to <<<javac>>> or other tasks:
- You can also use a Maven 2.0 POM to declare your dependencies, which is {{{examples/pom.html} described in the examples}}.
+ You can also use a Maven 2.0 POM to declare your dependencies, which is {{{./examples/pom.html} described in the examples}}.
This is the recommended practice so that you can reuse the file to deploy your own artifacts.
- For more examples of using the dependencies task, see the {{{examples/dependencies.html} examples page}}.
+ For more examples of using the dependencies task, see the {{{./examples/dependencies.html} examples page}}.
* Installing and Deploying Your Own Artifacts to a Repository
@@ -65,7 +65,7 @@
The <<<deploy>>> task allows artifacts to be deployed to a remote maven repository where they will
be available to other projects.
- For examples of using the install and deploy tasks, see the {{{examples/install-deploy.html} examples page}}.
+ For examples of using the install and deploy tasks, see the {{{./examples/install-deploy.html} examples page}}.
* Using a Maven {POM} File
@@ -76,7 +76,7 @@
It can also be reused for declaring your own dependencies, instead of specifying the inline version given earlier.
- For examples of creating a pom and using the <<<pom>>> task, see the {{{examples/pom.html}examples page}}.
+ For examples of creating a pom and using the <<<pom>>> task, see the {{{./examples/pom.html}examples page}}.
* Declaring Repositories
