You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2017/12/20 09:27:16 UTC
[maven-antrun-plugin] 07/26: convert docs to APT
This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a commit to annotated tag maven-antrun-plugin-1.1
in repository https://gitbox.apache.org/repos/asf/maven-antrun-plugin.git
commit b8e06225f046513fd57e665ac2f0e9957f91406c
Author: Brett Leslie Porter <br...@apache.org>
AuthorDate: Thu Nov 17 21:47:27 2005 +0000
convert docs to APT
git-svn-id: https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-antrun-plugin@345336 13f79535-47bb-0310-9956-ffa450edef68
---
src/site/apt/introduction.apt | 27 +++++++++++++++++++
src/site/{xdoc/usage.xml => apt/usage.apt} | 43 +++++++++++-------------------
src/site/xdoc/introduction.xml | 39 ---------------------------
3 files changed, 43 insertions(+), 66 deletions(-)
diff --git a/src/site/apt/introduction.apt b/src/site/apt/introduction.apt
new file mode 100644
index 0000000..a91a99e
--- /dev/null
+++ b/src/site/apt/introduction.apt
@@ -0,0 +1,27 @@
+ -----
+Introduction
+ -----
+Kenney Westerhof
+ -----
+10 August 2005
+ -----
+
+Introduction
+
+ This plugin provides the ability to run Ant tasks from
+ within Maven2. You can even embed your ant scripts in the POM!
+
+ It is <not> the intention of this plugin to provide a means
+ of polluting the POM, so it's encouraged to move all your
+ Ant tasks to a build.xml file and just call it from the POM
+ using Ant's {{{http://ant.apache.org/manual/CoreTasks/ant.html}\<ant/\> task}}.
+
+ One of the main goals of this plugin is to ease the migration from
+ Ant based projects to Maven 2. A lot of projects are currently unable
+ to migrate simply because they depend on some custom build functionality
+ that Maven2 doesn't provide yet.
+
+ Even with plugins widely available there will always be simple, small
+ tasks that can be done using one or two lines of Ant script (like
+ deploying an EAR), until ofcourse a plugin comes available that does
+ the job.
diff --git a/src/site/xdoc/usage.xml b/src/site/apt/usage.apt
similarity index 55%
rename from src/site/xdoc/usage.xml
rename to src/site/apt/usage.apt
index 7c930dc..87b0fac 100644
--- a/src/site/xdoc/usage.xml
+++ b/src/site/apt/usage.apt
@@ -1,19 +1,16 @@
-<?xml version="1.0"?>
+ ----
+Usage
+ ----
+Kenney Westerhof
+ ----
+10 August 2005
+ ----
-<document>
- <properties>
- <author email="kenney@apache.org">Kenney Westerhof</author>
- <title>Introduction</title>
- </properties>
- <head/>
- <body>
- <section name="Usage">
- <p>
- For those of you unfamiliar with configuring a plugin see the example
- below:
+Usage
- <source>
-<![CDATA[
+ For those of you unfamiliar with configuring a plugin see the example below:
+
+------
<project>
<modelVersion>4.0.0</modelVersion>
<artifactId>my-test-app</artifactId>
@@ -49,17 +46,9 @@
</plugins>
</build>
</project>
-]]>
- </source>
- </p>
-
- <p>
- The example above illustrates how to bind an ant script to a
- lifecycle phase. You can add a script to each lifecycle phase,
- by duplicating the <![CDATA[<execution/>]]> section and specifying
- a new phase.
- </p>
- </section>
+------
- </body>
-</document>
+ The example above illustrates how to bind an ant script to a
+ lifecycle phase. You can add a script to each lifecycle phase,
+ by duplicating the <<<\<execution/\>>>> section and specifying
+ a new phase.
diff --git a/src/site/xdoc/introduction.xml b/src/site/xdoc/introduction.xml
deleted file mode 100644
index 5434221..0000000
--- a/src/site/xdoc/introduction.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-<?xml version="1.0"?>
-
-<document>
- <properties>
- <author email="kenney@apache.org">Kenney Westerhof</author>
- <title>Introduction</title>
- </properties>
- <head/>
- <body>
- <section name="Introduction">
- <p>
- This plugin provides the ability to run Ant tasks from
- within Maven2. You can even embed your ant scripts in the POM!
- </p>
-
- <p>
- It is <emph>not</emph> the intention of this plugin to provide a means
- of polluting the POM, so it's encouraged to move all your
- Ant tasks to a build.xml file and just call it from the POM
- using Ant's <a href="http://ant.apache.org/manual/CoreTasks/ant.html"><ant/> task</a>.
- </p>
-
- <p>
- One of the main goals of this plugin is to ease the migration from
- Ant based projects to Maven 2. A lot of projects are currently unable
- to migrate simply because they depend on some custom build functionality
- that Maven2 doesn't provide yet.
- </p>
-
- <p>
- Even with plugins widely available there will always be simple, small
- tasks that can be done using one or two lines of Ant script (like
- deploying an EAR), until ofcourse a plugin comes available that does
- the job.
- </p>
-
- </section>
- </body>
-</document>
--
To stop receiving notification emails like this one, please contact
"commits@maven.apache.org" <co...@maven.apache.org>.