donaldp 2002/11/16 15:59:41
Modified: src/documentation/content Tag: FORREST-branch
getting-started.xml index.xml
src/documentation/content/framework Tag: FORREST-branch
index.xml reference-containers.xml
reference-the-lifecycle.xml
Log:
Remove remaining *_BASE tokens
Revision Changes Path
No revision
No revision
1.1.2.2 +6 -6
jakarta-avalon/src/documentation/content/Attic/getting-started.xml
Index: getting-started.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon/src/documentation/content/Attic/getting-started.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- getting-started.xml 16 Nov 2002 23:53:12 -0000 1.1.2.1
+++ getting-started.xml 16 Nov 2002 23:59:41 -0000 1.1.2.2
@@ -20,13 +20,13 @@
<p>An effort is underway to write a concise, example-oriented
guide
to avalon that will get you up and running in about 2 minutes.
You
can find the draft
- <link
href="@AVALON_BASE@/excalibur/tweety/avalon-for-beginners.html">here</link>.</p>
+ <link
href="excalibur/tweety/avalon-for-beginners.html">here</link>.</p>
</section>
<section>
<title>Developing with Avalon</title>
<p>Another really neat document is our
- <link href="@AVALON_BASE@/developing/">Developing with Avalon
whitepaper</link>.
+ <link href="developing/">Developing with Avalon
whitepaper</link>.
It's quite extensive, but very thorough and well-written. If
you're an
experienced software engineer, you'll definately appreciate
it.</p>
</section>
@@ -55,16 +55,16 @@
<title>Avalon Cornerstone</title>
<p>Much the same is true for the cornerstone
documentation. We
suggest you read the
- <link
href="@AVALON_BASE@/cornerstone">overview</link>, then
+ <link href="cornerstone">overview</link>, then
browse the
- <link
href="@AVALON_BASE@/cornerstone/api">javadocs</link>
+ <link href="cornerstone/api">javadocs</link>
for more information.</p>
</section>
<section>
<title>Avalon Phoenix</title>
<p>The
- <link
href="@AVALON_BASE@/phoenix/getting-started.html">Avalon Phoenix getting started
document</link>
+ <link href="phoenix/getting-started.html">Avalon
Phoenix getting started document</link>
desribes the HelloWorld demo Service demo. Tt will
take you
through downloading, installing and then running the
demo step
by step so it is an easy place tp start</p>
@@ -76,7 +76,7 @@
rather with Phoenix or another container, so you don't
normally
need to learn much about logkit. If you are interested
in learning
more about it, there's a really good
- <link
href="@AVALON_BASE@/logkit/whitepaper.html">whitepaper</link>
+ <link href="logkit/whitepaper.html">whitepaper</link>
on it (it doesn't have a real 'getting started'
document).</p>
</section>
1.1.2.2 +6 -6 jakarta-avalon/src/documentation/content/Attic/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon/src/documentation/content/Attic/index.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- index.xml 16 Nov 2002 23:53:12 -0000 1.1.2.1
+++ index.xml 16 Nov 2002 23:59:41 -0000 1.1.2.2
@@ -74,7 +74,7 @@
<section>
<title>Excalibur</title>
<p>
- <link href="@EXCALIBUR_BASE@/index.html">Excalibur</link> is a collection
of
+ <link href="excalibur/index.html">Excalibur</link> is a collection of
implementations and common code based on and implementing the
<link href="framework/index.html">Avalon Framework</link>.
</p>
@@ -83,7 +83,7 @@
<section>
<title>Phoenix</title>
<p>
- <link href="@PHOENIX_BASE@/index.html">Phoenix</link> is a server oriented
+ <link href="phoenix/index.html">Phoenix</link> is a server oriented
Application Server. Applications and Services that conform to the
framework
rules can be hosted in Phoenix. The Application server manages the
applications
classloader, security and logging needs. It also provides a JMX-based
management
@@ -94,8 +94,8 @@
<section>
<title>Cornerstone</title>
<p>
- <link href="@CORNERSTONE_BASE@/index.html">Cornerstone</link> is a
repository.
- for what we call <link
href="@PHOENIX_BASE@/what-is-a-block.html">blocks</link>,
+ <link href="cornerstone/index.html">Cornerstone</link> is a repository.
+ for what we call <link href="phoenix/what-is-a-block.html">blocks</link>,
which provide services vital to server applications. The blocks include
blocks for
services such as scheduling and socket management.
</p>
@@ -104,7 +104,7 @@
<section>
<title>Applications</title>
<p>
- <link href="@APPS_BASE@/index.html">Applications</link> is a repository of
+ <link href="apps/index.html">Applications</link> is a repository of
Phoenix blocks. Some are simple self-contained demos of Phoenix
applications,
others are complete standalone products, and a few are ambitious works in
progress.
If you are looking for a starting point for a Phoenix block or a complete
server,
@@ -115,7 +115,7 @@
<section>
<title>LogKit</title>
<p>
- <link href="@LOGKIT_BASE@/index.html">LogKit</link> is the preferred
logging toolkit
+ <link href="logkit/index.html">LogKit</link> is the preferred logging
toolkit
used by the Avalon subprojects.</p>
<p>
It is quite possible to use the other avalon subprojects without committing
to logkit.
No revision
No revision
1.1.2.2 +1 -1
jakarta-avalon/src/documentation/content/framework/Attic/index.xml
Index: index.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon/src/documentation/content/framework/Attic/index.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- index.xml 16 Nov 2002 23:53:16 -0000 1.1.2.1
+++ index.xml 16 Nov 2002 23:59:41 -0000 1.1.2.2
@@ -79,7 +79,7 @@
<title>Avalon Framework Reference Documentation</title>
<p>
Besides the
- <link href="@AVALON_BASE@/api/index.html">Javadocs</link>, we have
+ <link href="../api/index.html">Javadocs</link>, we have
<link href="diagrams/">Class diagrams</link>, the
<link href="reference-the-lifecycle.html">Lifecycle specification</link>
and the
<link href="reference-containers.html">List of containers</link>.
1.1.2.2 +2 -2
jakarta-avalon/src/documentation/content/framework/Attic/reference-containers.xml
Index: reference-containers.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon/src/documentation/content/framework/Attic/reference-containers.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- reference-containers.xml 16 Nov 2002 23:53:16 -0000 1.1.2.1
+++ reference-containers.xml 16 Nov 2002 23:59:41 -0000 1.1.2.2
@@ -29,7 +29,7 @@
as hosted components. These can be applications like a web server, RDBMS or
EJB server. It provides many advanced features like automatic management, at
the
cost of a bit of complexity.
- See <link href="@PHOENIX_BASE@/index.html">Phoenix</link>.
+ See <link href="../phoenix/index.html">Phoenix</link>.
</p>
<p>
@@ -46,7 +46,7 @@
exclusively as a teaching tool. It has no features whatsoever besides basic
support
for the avalon lifecycle. This results in a complete distribution the size of
the
phoenix bootstrapper.
- See <link href="@AVALON_BASE@/excalibur/tweety">Tweety</link>
+ See <link href="../excalibur/tweety">Tweety</link>
</p>
</section>
1.1.2.2 +1 -1
jakarta-avalon/src/documentation/content/framework/Attic/reference-the-lifecycle.xml
Index: reference-the-lifecycle.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon/src/documentation/content/framework/Attic/reference-the-lifecycle.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- reference-the-lifecycle.xml 16 Nov 2002 23:53:16 -0000 1.1.2.1
+++ reference-the-lifecycle.xml 16 Nov 2002 23:59:41 -0000 1.1.2.2
@@ -20,7 +20,7 @@
<p>
The Avalon project provides an
application that functions as a container for componentized applications
- called <link href="@PHOENIX_BASE@/index.html">Phoenix</link>. This is not
+ called <link href="../phoenix/index.html">Phoenix</link>. This is not
exclusive, components adhering to lifecycle interfaces, can be mounted in
custom containers. Cocoon and others mounts their own containers for
components and invoke relevant methods from the lifecycle interfaces. See
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
