leosimons 2003/10/28 14:53:47
Modified: src/documentation skinconf.xml
src/documentation/content/xdocs index.xml tabs.xml
Removed: src/documentation sitemap-0.5.xmap sitemap.xmap
Log:
make things work with latest forrest from cvs
Revision Changes Path
1.8 +4 -4 avalon-phoenix/src/documentation/skinconf.xml
Index: skinconf.xml
===================================================================
RCS file: /home/cvs/avalon-phoenix/src/documentation/skinconf.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- skinconf.xml 5 Oct 2003 06:46:06 -0000 1.7
+++ skinconf.xml 28 Oct 2003 22:53:47 -0000 1.8
@@ -50,13 +50,13 @@
<!-- mandatory project logo
skin: forrest-site renders it at the top -->
- <project-name>Avalon Phoenix</project-name>
- <project-url>http://avalon.apache.org/phoenix/</project-url>
- <project-logo>images/header.gif</project-logo>
+ <project-name>Visit ApacheCon 2003!</project-name>
+ <project-url>http://apachecon.com/2003/US/index.html</project-url>
+ <project-logo>http://www.apache.org/~ceki/ac2003/ac2003-150.gif</project-logo>
<!-- optional group logo
skin: forrest-site renders it at the top-left corner -->
- <group-name>Apache Avalon</group-name>
+ <group-name>Apache Avalon-Phoenix</group-name>
<group-url>http://avalon.apache.org/</group-url>
<group-logo>images/apache-avalon-logo.png</group-logo>
1.5 +97 -63 avalon-phoenix/src/documentation/content/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-phoenix/src/documentation/content/xdocs/index.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- index.xml 7 Feb 2003 15:35:58 -0000 1.4
+++ index.xml 28 Oct 2003 22:53:47 -0000 1.5
@@ -1,69 +1,103 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
"document-v11.dtd">
<document>
- <header>
- <title>Overview</title>
-
- <authors><person name="Phoenix Documentation Team" email="[EMAIL
PROTECTED]"/></authors></header>
- <body>
- <section><title>Introduction</title>
- <p>
- Phoenix is a micro-kernel designed and implemented on top of the Avalon
- framework.
- It provides a number of facilities to manage the
- environment of Server Applications. Such facilities include log management,
- classloading, thread management and security. In the future it will
- conditionally support extra facilities such as central server management,
- server pools, and other facilities aimed at reducing the time to market.
The API
- defines a standard method of piecing together server components and
creating a server.
- </p>
- </section>
- <section><title>Documentation is coming</title>
- <p>
- Some of the information on this site is currently a bit out of date. We are
- working hard to fix this. If you come across any inconsistencies or have a
- problem, please don't hesitate to contact us through the mailing list. Thank
- you.
- </p>
- </section>
- <section><title>Guide to Avalon Phoenix</title>
- <p>
- This guide starts with an architectural overview of Phoenix. Then, we
identify
- the different roles that typically exist in daily use of phoenix. For each of
- these, we provide a basic guide. We finish with a complete example.
- </p>
- <section><title>Target Audience</title>
- <p>
- This documentation is aimed towards people who:
- </p><ul>
- <li>wish to create applications that run within phoenix</li>
- <li>wish to create components (blocks) for use within phoenix</li>
- <li>wish to setup and administer phoenix</li>
- <li>are interested in the design principles of Avalon Phoenix</li>
- <li>wish to develop code that will be incorporated into Avalon
Phoenix</li>
- <li>wish to reuse Avalon Phoenix concepts in their own
application</li>
- </ul><p>
- </p>
+ <header>
+ <title>Welcome to Avlaon-Phoenix!</title>
+
+ <authors>
+ <person name="Phoenix Documentation Team" email="[EMAIL PROTECTED]"/>
+ </authors>
+ </header>
+ <body>
+ <section>
+ <title>Introduction</title>
+ <p>
+ Phoenix is a micro-kernel designed and implemented on top of the
Avalon
+ framework.
+ It provides a number of facilities to manage the
+ environment of Server Applications. Such facilities include log
management,
+ classloading, thread management and security. In the future it will
+ conditionally support extra facilities such as central server
management,
+ server pools, and other facilities aimed at reducing the time to
market. The API
+ defines a standard method of piecing together server components and
creating a server.
+ </p>
</section>
- <section><title>Contents</title>
- <ol>
- <li><link href="guide-architecture.html">Architectural
overview</link></li>
- <li><link href="guide-roles.html">Development roles</link></li>
- <li><link href="guide-administrator.html">Administrator
Guide</link></li>
- <li><link href="guide-deployers.html">Application Deployer
Guide</link></li>
- <li><link href="mx/index.html">JMX Management Guide</link></li>
- <li><link href="assemblers/index.html">Server Application Assembler
Guide</link></li>
- <li><link href="bdg/index.html">Block Developer Guide</link></li>
- <li><link href="guide-example-configuration.html">Example
Configuration.</link></li>
- </ol>
+ <section>
+ <title>Also see...</title>
+ <p>
+ Phoenix is no longer under active development. Most of the avalon
container
+ development efforts are focussed on
+ <link href="http://avalon.apache.org/merlin/";>Merlin</link>. If you
are
+ evaluating what container to use, we suggest you try merlin first
to see if
+ it meets your needs.
+ </p>
+ <p>
+ Alternatively, you might want to look at
+ <link href="http://jcontainer.org/loom/";>Loom</link>, which started
out as a
+ fork of Phoenix 4.1-dev and shares many of its features. Please do
note that
+ Loom is not a part of avalon nor of the ASF.
+ </p>
</section>
- </section>
- <section><title>Avalon Phoenix Reference Documentation</title>
- <p>
- Besides the
- <link href="api/index.html">Javadocs</link>, we have the
- <link href="guide-architecture.html">Architectural overview</link> to look
at.
- </p>
- </section>
- </body>
+ <section>
+ <title>Guide to Avalon Phoenix</title>
+ <p>
+ This guide starts with an architectural overview of Phoenix. Then,
we identify
+ the different roles that typically exist in daily use of phoenix.
For each of
+ these, we provide a basic guide. We finish with a complete example.
+ </p>
+ <section>
+ <title>Target Audience</title>
+ <p>
+ This documentation is aimed towards people who:
+ </p>
+ <ul>
+ <li>wish to create applications that run within phoenix</li>
+ <li>wish to create components (blocks) for use within
phoenix</li>
+ <li>wish to setup and administer phoenix</li>
+ <li>are interested in the design principles of Avalon
Phoenix</li>
+ <li>wish to develop code that will be incorporated into Avalon
Phoenix</li>
+ <li>wish to reuse Avalon Phoenix concepts in their own
application</li>
+ </ul>
+ <p>
+ </p>
+ </section>
+ <section>
+ <title>Contents</title>
+ <ol>
+ <li>
+ <link href="guide-architecture.html">Architectural
overview</link>
+ </li>
+ <li>
+ <link href="guide-roles.html">Development roles</link>
+ </li>
+ <li>
+ <link href="guide-administrator.html">Administrator
Guide</link>
+ </li>
+ <li>
+ <link href="guide-deployers.html">Application Deployer
Guide</link>
+ </li>
+ <li>
+ <link href="mx/index.html">JMX Management Guide</link>
+ </li>
+ <li>
+ <link href="assemblers/index.html">Server Application
Assembler Guide</link>
+ </li>
+ <li>
+ <link href="bdg/index.html">Block Developer Guide</link>
+ </li>
+ <li>
+ <link href="guide-example-configuration.html">Example
Configuration.</link>
+ </li>
+ </ol>
+ </section>
+ </section>
+ <section>
+ <title>Avalon Phoenix Reference Documentation</title>
+ <p>
+ Besides the
+ <link href="api/index.html">Javadocs</link>, we have the
+ <link href="guide-architecture.html">Architectural overview</link>
to look at.
+ </p>
+ </section>
+ </body>
</document>
1.5 +8 -10 avalon-phoenix/src/documentation/content/xdocs/tabs.xml
Index: tabs.xml
===================================================================
RCS file: /home/cvs/avalon-phoenix/src/documentation/content/xdocs/tabs.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- tabs.xml 6 Apr 2003 01:20:19 -0000 1.4
+++ tabs.xml 28 Oct 2003 22:53:47 -0000 1.5
@@ -1,16 +1,14 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab V1.0//EN"
"tab-cocoon-v10.dtd">
- <tabs software="MyProj"
+<tabs software="MyProj"
title="MyProj"
- copyright="Foo"
- xmlns:xlink="http://www.w3.org/1999/xlink";>
+ copyright="Foo">
- <tab label="Framework" href="http://avalon.apache.org/framework/"/>
- <tab label="Excalibur" href="http://avalon.apache.org/excalibur/"/>
- <tab label="Cornerstone" href="http://avalon.apache.org/cornerstone/"/>
- <tab label="Phoenix" dir="/"/>
- <tab label="Apps" href="http://avalon.apache.org/apps/"/>
- <tab label="Logkit" href="http://avalon.apache.org/logkit/"/>
+ <tab label="Apache" href="http://www.apache.org/"/>
+ <tab label="Avalon" href="http://avalon.apache.org/"/>
+ <tab label="Framework" href="http://avalon.apache.org/product/framework/"/>
+ <tab label="Containers" href="http://avalon.apache.org/product/containers/"/>
+ <tab label="Components" href="http://avalon.apache.org/product/components/"/>
- </tabs>
+</tabs>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
