You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by di...@apache.org on 2004/02/03 01:38:26 UTC
cvs commit: maven/xdocs/start anakia.xml
dion 2004/02/02 16:38:26
Modified: xdocs/start Tag: MAVEN-1_0-BRANCH anakia.xml
Log:
Apply MAVEN-1114
Revision Changes Path
No revision
No revision
1.7.10.1 +43 -54 maven/xdocs/start/anakia.xml
Index: anakia.xml
===================================================================
RCS file: /home/cvs/maven/xdocs/start/anakia.xml,v
retrieving revision 1.7
retrieving revision 1.7.10.1
diff -u -r1.7 -r1.7.10.1
--- anakia.xml 17 Jul 2003 01:20:09 -0000 1.7
+++ anakia.xml 3 Feb 2004 00:38:26 -0000 1.7.10.1
@@ -1,40 +1,34 @@
<?xml version="1.0"?>
<document>
-
- <properties>
- <title>Anakia to Maven</title>
- <author email="pete-apache-dev@kazmier.com">Pete Kazmier</author>
- </properties>
-
- <body>
- <section name="Anakia to Maven">
- <p>
- This document has been specifically created for users of Anakia.
- If you use Anakia to generate a website for your project, you
- can easily migrate to Maven and automatically inherit a great
- look and feel designed by CSS experts. This is an ideal
- opportunity for you to start integrating Maven into your
- project. Using Maven is not an all or nothing scenario, with
- very little effort you can use Maven to generate only your site
- documentation. As you become more familiar with Maven, you can
- then slowly start utilizing other features of Maven.
- </p>
- <p>
- The process of creating a Maven-generated site from your Anakia
- documentation is outlined below:
- </p>
- <ul>
+ <properties>
+ <title>Anakia to Maven</title>
+ <author email="pete-apache-dev@kazmier.com">Pete Kazmier</author>
+ </properties>
+ <body>
+ <section name="Anakia to Maven">
<p>
+ This document has been specifically created for users of Anakia.
+ If you use Anakia to generate a website for your project, you
+ can easily migrate to Maven and automatically inherit a great
+ look and feel designed by CSS experts. This is an ideal
+ opportunity for you to start integrating Maven into your
+ project. Using Maven is not an all or nothing scenario, with
+ very little effort you can use Maven to generate only your site
+ documentation. As you become more familiar with Maven, you can
+ then slowly start utilizing other features of Maven.
+ </p>
+ <p>
+ The process of creating a Maven-generated site from your Anakia
+ documentation is outlined below:
+ </p>
+ <ul>
<li>
Install Maven on your system. Please refer to the
<a href="index.html">Getting Started</a>
documentation for assistance.
</li>
- </p>
- <p>
<li>
- Create a project descriptor and refer to the <a
- href="integrate.html">Integration</a> document for
+ Create a project descriptor and refer to the <a href="integrate.html">Integration</a> document for
assistance. You'll also be able to change the default colors
used by Maven when generating your site by setting the
appropriate properties. If you are only interested in using
@@ -42,37 +36,32 @@
you do not have to complete the &lt;build&gt; element
section of the project descriptor.
</li>
- </p>
- <p>
<li>
Use Maven to generate your site by invoking the
<code>maven site</code> goal. You can also
automatically deploy your site to a web server with
<code>maven site:deploy</code>.
</li>
+ </ul>
+ <p>
+ If your project does not store its documentation in the
+ <code>xdocs</code> directory located in the base directory of
+ the project, you'll have to define the property
+ <code>${maven.docs.src}</code> in a properties file or via the command
+ line to point to the appropriate location.
+ </p>
+ <p>
+ Prior to writing this document, several random Jakarta projects
+ were selected and their documentation was generated using Maven
+ to demonstrate how easy it is to switch from Anakia to Maven.
+ Give it a try, we promise you'll like it!
+ </p>
+ </section>
+ <section name="Anakia Extensions">
+ <p>
+ See <a href="/site.html">Site Navigation</a> for more information about
+ Maven extensions to Anakia.
</p>
- </ul>
- <p>
- If your project does not store its documentation in the
- <code>xdocs</code> directory located in the base directory of
- the project, you'll have to define the property
- <code>${maven.docs.src}</code> in a properties file or via the command
- line to point to the appropriate location.
- </p>
- <p>
- Prior to writing this document, several random Jakarta projects
- were selected and their documentation was generated using Maven
- to demonstrate how easy it is to switch from Anakia to Maven.
- Give it a try, we promise you'll like it!
- </p>
-
- </section>
-
- <section name="Anakia Extensions">
- <p>
- See <a href="/site.html">Site Navigation</a> for more information about
- Maven extensions to Anakia.
- </p>
- </section>
- </body>
+ </section>
+ </body>
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org