leosimons 2003/02/03 07:43:39
Modified: src/documentation/content/history index.xml
src/documentation/content/xdocs book.xml case-studies.xml
code-standards.xml cvs.xml features.xml
getting-started.xml index.xml mailing-lists.xml
news.xml
src/documentation/content/xdocs/components index.xml
src/documentation/content/xdocs/history index.xml
src/documentation/content/xdocs/project book.xml patches.xml
pmc.xml releases.xml roadmap.xml
src/documentation/content/xdocs/seca index.xml
Log:
Applying patch from bug 16620
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16620), fixing lots of typos.
Submitted by [EMAIL PROTECTED] (Ulrich Mayring). Thanks Ulrich!
Revision Changes Path
1.2 +3 -3 jakarta-avalon-site/src/documentation/content/history/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-site/src/documentation/content/history/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 29 Jan 2003 13:31:20 -0000 1.1
+++ index.xml 3 Feb 2003 15:43:38 -0000 1.2
@@ -30,12 +30,12 @@
<p>
Over time the Java Apache Server Framework project was renamed Avalon. This was
in
- recognition that the original ideas have evolved over time. Avalon became a
+ recognition that the original ideas had evolved over time. Avalon became a
repository of general utility code, a design and testing ground for component
based
- solutions, a micro kernel and set of generalized server oriented services. This
combined
+ solutions, a micro kernel and set of generalized server oriented services.
This, combined
with a move from the Java Apache project to the Jakarta project prompted the
revision.
At this time the kernel code was repackaged under the name Phoenix, core
services
- under the name Cornerstone and the general components was packaged under name
Excalibur.
+ under the name Cornerstone and the general components were packaged under the
name Excalibur.
</p>
<p>
You may check the historical changes from before splitting Avalon into separate
projects <link href="changes.html">here</link>.
1.6 +4 -4 jakarta-avalon-site/src/documentation/content/xdocs/book.xml
Index: book.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/book.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- book.xml 29 Jan 2003 13:33:05 -0000 1.5
+++ book.xml 3 Feb 2003 15:43:38 -0000 1.6
@@ -11,10 +11,10 @@
<menu-item label="Mission" href="mission.html"/>
<menu-item label="News and Status" href="news.html"/>
<menu-item label="Features" href="features.html"/>
- <menu-item label="Download binaries" href="bindownload.cgi"/>
- <menu-item label="Download sources" href="srcdownload.cgi"/>
+ <menu-item label="Download Binaries" href="bindownload.cgi"/>
+ <menu-item label="Download Sources" href="srcdownload.cgi"/>
<menu-item label="License" href="license.html"/>
- <menu-item label="Who we are" href="whoweare/index.html"/>
+ <menu-item label="Who we Are" href="whoweare/index.html"/>
</menu>
<menu label="Subprojects">
@@ -40,7 +40,7 @@
</menu>
<menu label="Development">
- <menu-item label="Coding standards" href="code-standards.html"/>
+ <menu-item label="Coding Standards" href="code-standards.html"/>
<menu-item label="Get Involved" href="http://james.apache.org/contribute.html"/>
<menu-item label="Project Guidelines" href="project/index.html"/>
<menu-item label="Project History" href="history/index.html"/>
1.2 +1 -1
jakarta-avalon-site/src/documentation/content/xdocs/case-studies.xml
Index: case-studies.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/case-studies.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- case-studies.xml 24 Jan 2003 19:39:40 -0000 1.1
+++ case-studies.xml 3 Feb 2003 15:43:38 -0000 1.2
@@ -43,7 +43,7 @@
<title>eQ!(tm)</title>
<p>A commercial product from Browsersoft, Inc., eQ!(tm) is a business object
foundation
which has recently been refactored and built upon Avalon and utilizes several
of
- Excalibur's components for it's persistence engine, XML-based scripting
engine,
+ Excalibur's components for its persistence engine, XML-based scripting engine,
Struts adapters and other internal usages.</p>
<p>eQ!(tm)'s goal is to provide a foundation upon which to build delivery
technology
1.3 +8 -9
jakarta-avalon-site/src/documentation/content/xdocs/code-standards.xml
Index: code-standards.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/code-standards.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- code-standards.xml 25 Jan 2003 17:19:00 -0000 1.2
+++ code-standards.xml 3 Feb 2003 15:43:38 -0000 1.3
@@ -14,10 +14,10 @@
<title>Coding Standards</title>
<p>This document describes a list of coding conventions that are required
for code submissions to the project. By default, the coding conventions
- for most Open Source Projects should follow the existing coding conventions
+ for most Open Source projects should follow the existing coding conventions
in the code that you are working on. For example, if the bracket is on
the same line as the if statement, then you should write all your code
- to have that convention.</p>
+ to follow that convention.</p>
<p><strong>Please follow these conventions closely. It makes life so much
easier.</strong></p>
@@ -87,14 +87,14 @@
of each and every file.</p>
<p>If you contribute to a file (code or documentation), add yourself to the
-top of the file. For java files the preferred Javadoc format is:</p>
+top of the file. For .java files the preferred Javadoc format is:</p>
<source>
@author <a href="mailto:[EMAIL PROTECTED]">John Doe</a>
</source>
<p>Indent comments on an 80 column basis and the code on a
- 100 column, using a two more indents when a line must be wrapped.</p>
+ 100 column basis, using two more indents when a line must be wrapped.</p>
<p>We focus on readability over performance, at least initially. Source code
optimization is the last thing to be done to increase performance.
@@ -116,10 +116,10 @@
}
</source>
-<p>Variable should be descriptive and ideally English words. The exceptions
-being; loop counters (usually use i, j and k), exceptions (use concatenation
-of word separating characters - ie SocketException is abbreviated as se) and
-other commonly used abbreviations (ie sb for StringBuffer).</p>
+<p>Variables should be descriptive and ideally English words. The exceptions
+being loop counters (usually use i, j and k), exceptions (use concatenation
+of word separating characters - i.e. SocketException is abbreviated as se) and
+other commonly used abbreviations (i.e. sb for StringBuffer).</p>
<source>
try
{
@@ -187,7 +187,6 @@
<source>
final MySomething something = myObject.doSomething();
final MyElse somethingElse = something.doSomethingElse();
-
Thing thing = somethingElse.getMyThing();
</source>
<p>The extra typing will help keep the code bug-free.</p>
1.3 +34 -34 jakarta-avalon-site/src/documentation/content/xdocs/cvs.xml
Index: cvs.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/cvs.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- cvs.xml 25 Jan 2003 17:12:52 -0000 1.2
+++ cvs.xml 3 Feb 2003 15:43:38 -0000 1.3
@@ -13,15 +13,15 @@
<section>
<title>Bleeding-edge only</title>
- <p>If you are looking to download the source code for stable versions of the
avalon
+ <p>If you are looking to download the source code for stable versions of the
Avalon
projects, you're in the wrong place. You should download a source release from
- <link href="srcdownload.cgi">the source download page</link></p>
+ <link href="srcdownload.cgi">the source download page</link>.</p>
</section>
<section>
<title>About CVS</title>
<p>CVS, the Concurrent Versions System is a revision control system useful for
management of source code, and is the predominant version control system used
at
- apache. See <link href="http://www.cvshome.org/";>The CVS Homepage</link> for
+ Apache. See <link href="http://www.cvshome.org/";>The CVS Homepage</link> for
more about CVS.</p>
</section>
<section>
@@ -42,22 +42,22 @@
</source>
</section>
<section>
- <title>Getting the sources from CVS under windows</title>
+ <title>Getting the sources from CVS under Windows</title>
<p>There's a few options for you:</p>
<section>
<title>Use cygwin</title>
<p><link href="http://www.cygwin.com/";>Cygwin</link> is a free
software suite
- of ports of popular linux tools and utilities to run natively under
windows.
- Among it is a port of the cvs application. If you use cygwin, follow
the linux
+ of ports of popular Linux tools and utilities to run natively under
windows.
+ Among it is a port of the cvs application. If you use cygwin, follow
the Linux
instructions.</p>
</section>
<section>
- <title>Use the commandline tools</title>
+ <title>Use the command-line tools</title>
- <p>The CVS utilities are available as native windows binaries. Get
them from
- <link href="http://www.cvshome.org/";>The CVS Homepage</link>. To use
these
+ <p>The CVS utilities are available as native Windows binaries. Get
them from
+ <link href="http://www.cvshome.org/";>the CVS homepage</link>. To use
these
tools, open a command window (click Start > Run..., then type 'cmd'),
then
enter the following commands:</p>
@@ -68,7 +68,7 @@
mkdir C:\cvs
cd C:\cvs
$CVSUTILS\cvs.exe -d :pserver:[EMAIL PROTECTED] login
-rem enter anoncvs when promted for a password, then hit enter
+rem enter anoncvs when prompted for a password, then hit enter
rem the below command should be on one line
$CVSUTILS\cvs.exe -z3 -d :pserver:[EMAIL PROTECTED] checkout jakarta-avalon
jakarta-avalon-excalibur jakarta-avalon-cornerstone
@@ -77,7 +77,7 @@
</source>
<p>This will take a while, depending on your connection. Go ahead and
grab
- yourself a coffee or ten. When done, you should have checked out all
avalon
+ yourself a coffee or ten. When done, you should have checked out all
Avalon
sources and the most important utility libraries you need to build it
(save
for <link href="http://ant.apache.org/";>Apache Ant</link>, which you
should
go install right now if you haven't already).</p>
@@ -86,55 +86,55 @@
<title>Use TortoiseCVS</title>
<p><link href="http://www.tortoisecvs.org/";>TortoiseCVS</link> is a
neat extension
- for the Windows Explorer which integrates cvs. Using it is real
simple:</p>
+ for the Windows Explorer which integrates CVS. Using it is real
simple:</p>
<p>After you've created a folder where you want to check out the
sources to,
right-click and select CVS Checkout...:<br/>
- <img src="images/tortoisecvs-checkout.jpg" alt="screenshot of cvs
settings"/></p>
+ <img src="images/tortoisecvs-checkout.jpg" alt="screenshot of CVS
settings"/></p>
<p>Then, fill out the settings like in the screenshot below, and then
click ok.<br/>
- <img src="images/tortoisecvs-settings.jpg" alt="screenshot of cvs
settings"/></p>
+ <img src="images/tortoisecvs-settings.jpg" alt="screenshot of CVS
settings"/></p>
- <p>This checks out the jakarta-avalon cvs module. Repeat this
procedure for all
- the modules you wish to check out. See above under "CVS Data" for the
list of avalon modules, or use the
+ <p>This checks out the jakarta-avalon CVS module. Repeat this
procedure for all
+ the modules you wish to check out. See above under "CVS data" for the
list of Avalon modules, or use the
<link href="http://cvs.apache.org/viewcvs.cgi/";>ViewCVS Webpage</link>
for a full
- list of ASF-hosted cvs modules.</p>
+ list of ASF-hosted CVS modules.</p>
</section>
<section>
<title>Use WinCVS</title>
<p><link href="http://www.wincvs.org/";>WinCVS</link> is a standalone
windows
- application for working with cvs. It has more features than
TortoiseCVS, and
+ application for working with CVS. It has more features than
TortoiseCVS, and
hence more buttons a novice is not likely to use.</p>
<p>After you've created a folder where you want to check out the
sources to,
select the Checkout module... option from the Create menu:<br/>
- <img src="images/wincvs-checkout.jpg" alt="screenshot of cvs
settings"/></p>
+ <img src="images/wincvs-checkout.jpg" alt="screenshot of CVS
settings"/></p>
<p>Then, select the "general tab" and fill out the settings like in the
screenshot below:<br/>
- <img src="images/wincvs-preferences.jpg" alt="screenshot of cvs
settings"/>.</p>
+ <img src="images/wincvs-preferences.jpg" alt="screenshot of CVS
settings"/>.</p>
<p>Now, switch back to the first tab and fill out the settings like in
the
screenshot below, and then click ok.<br/>
- <img src="images/wincvs-checkout.jpg" alt="screenshot of cvs
settings"/>.</p>
+ <img src="images/wincvs-checkout.jpg" alt="screenshot of CVS
settings"/>.</p>
- <p>This checks out the jakarta-avalon cvs module. Repeat this
procedure for all
- the modules you wish to check out. See above under "CVS Data" for the
list of avalon modules, or use the
- <link href="http://cvs.apache.org/viewcvs.cgi/";>ViewCVS Webpage</link>
for a full
- list of ASF-hosted cvs modules.</p>
+ <p>This checks out the jakarta-avalon CVS module. Repeat this
procedure for all
+ the modules you wish to check out. See above under "CVS data" for the
list of Avalon modules, or use the
+ <link href="http://cvs.apache.org/viewcvs.cgi/";>ViewCVS webpage</link>
for a full
+ list of ASF-hosted CVS modules.</p>
</section>
</section>
<section>
- <title>Getting the sources from CVS under linux</title>
+ <title>Getting the sources from CVS under Linux</title>
<section>
- <title>Use the commandline tools</title>
+ <title>Use the command-line tools</title>
<p>The CVS utilities are available as native linux binaries. Chances
are
you already have them installed. Try it by opening a console and
typing 'cvs'.
If you get an error along the lines of "bash: cvs: command not found",
then
- you need to install them first. Under debian, you can do so by opening
a console
+ you need to install them first. Under Debian, you can do so by opening
a console
window and entering the commands:</p>
<source>
@@ -154,7 +154,7 @@
exit
</source>
- <p>The procedure is similar for other linux distributions. Once you
have
+ <p>The procedure is similar for other Linux distributions. Once you
have
these tools installed, open a command window, then enter the following
commands:</p>
@@ -163,7 +163,7 @@
mkdir ~/cvs
cd ~/cvs
cvs -d :pserver:[EMAIL PROTECTED] login
-# enter anoncvs when promted for a password, then hit enter
+# enter anoncvs when prompted for a password, then hit enter
cvs -z3 -d :pserver:[EMAIL PROTECTED] checkout jakarta-avalon \
jakarta-avalon-excalibur jakarta-avalon-cornerstone \
jakarta-avalon-phoenix jakarta-avalon-logkit jakarta-avalon-site \
@@ -182,22 +182,22 @@
<p>KDE's Konqueror browser has CVS support built-in. I've never used
it so I
can't comment on it. See
- <link href="http://cervisia.sourceforge.net/";>the cervisia
website</link> for
+ <link href="http://cervisia.sourceforge.net/";>the Cervisia
website</link> for
more information.</p>
</section>
</section>
<section>
<title>Platform-independent: jCVS</title>
- <p><link href="http://www.jcvs.org/";>jCVS</link> is a 100% java cvs package
that I've
+ <p><link href="http://www.jcvs.org/";>jCVS</link> is a 100% java CVS package
that I've
never used.</p>
</section>
<section>
<title>Using an IDE for CVS access</title>
- <p>Most decent IDEs these days provide cvs integration. See the
+ <p>Most decent IDEs these days provide CVS integration. See the
<link href="http://jakarta.apache.org/site/idedevelopers.html";>IDE Developer's
Guide</link>
- if you need information on how to configure your ide.</p>
+ if you need information on how to configure your IDE.</p>
</section>
</body>
1.2 +13 -13 jakarta-avalon-site/src/documentation/content/xdocs/features.xml
Index: features.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/features.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- features.xml 24 Jan 2003 19:39:40 -0000 1.1
+++ features.xml 3 Feb 2003 15:43:38 -0000 1.2
@@ -15,23 +15,23 @@
<title>Introduction</title>
<p>The Avalon project is so large and broad in scope that it is not easy
to provide a simple list of features in the form of "Avalon provides
- Component X which will fulfill role Y in your project Z perfectly".</p>
+ component X which will fulfill role Y in your project Z perfectly".</p>
<p>Most of Avalon is oriented towards server development (though many parts
can be, and are, used in other software domains). As such, it delivers all
- those features server applications require (stability, performance, etc),
+ those features server applications require (stability, performance, etc.),
and does so very well.</p>
<section>
<title>Avalon Framework</title>
- <p>At the very core of our project is the Avalon Framework subproject.
+ <p>At the very core of our project is the Avalon Framework sub-project.
This framework is very stable and in daily use in many applications, from
straightforward desktop products to large scale enterprise applications.<br/>
After an initial learning curve, this framework will help you
- create a better software architecture. In this way, it's role is as
+ create a better software architecture. In this way, its role is as
fundamental as, say Object-Oriented Programming or Design Patterns.</p>
- <p>All other avalon subprojects make use of the framework. This has allowed
+ <p>All other Avalon sub-projects make use of the framework. This has allowed
us to provide truly pluggable components which can be used in any
programming environment without requiring gargantuan supporting
applications.</p>
</section>
@@ -54,7 +54,7 @@
<section>
<title>Avalon LogKit</title>
<p>Avalon LogKit is a feature-rich logging package. It can be used as an
- Alternative to other logging packages like Jakarta's
+ alternative to other logging packages like Jakarta's
<link href="http://jakarta.apache.org/log4j";>Log4J</link> or the (massively
inferior)
<link
href="http://java.sun.com/j2se/1.4/docs/guide/util/logging/index.html";>Logging
API</link>
@@ -68,12 +68,12 @@
<section>
<title>Avalon Phoenix</title>
<p>Phoenix is a micro-kernel. It takes care of low level application details
- so you can focus on your unique requirments. While this may sound to you
- like a servlet or EJB container, phoenix has a very different scope. Where
- you can use EJBs to connect to a database, phoenix is the basis on which to
+ so you can focus on your unique requirements. While this may sound to you
+ like a servlet or EJB container, Phoenix has a very different scope. Where
+ you can use EJBs to connect to a database, Phoenix is the basis on which to
run that database.<br/>
- With that said, you may now start to see the phoenix edge: it provides all
- of the features that make you love Servlet Engines so much (and several
+ With that said, you may now start to see the Phoenix edge: it provides all
+ of the features that make you love servlet engines so much (and several
more), without restricting you to the specific servlet use case. You can
use Avalon Phoenix to run your servlet engine, database, and other server
components, as well as your java-enabled desktop.</p>
@@ -86,10 +86,10 @@
<section>
<title>Avalon Applications</title>
- <p>Avalon Applications is a repository for Phoenix-enabled Applications.
+ <p>Avalon Applications is a repository for Phoenix-enabled applications.
It contains a JDBC-compliant database, a Macromedia Flash-compatible XML socket
server, and more. You'll also find a list of applications elsewhere on the
- web that run on phoenix. Go to the
+ web that run on Phoenix. Go to the
<link href="http://jakarta.apache.org/avalon/apps";>
Applications project page
</link> to find out all about them.</p>
1.2 +16 -16
jakarta-avalon-site/src/documentation/content/xdocs/getting-started.xml
Index: getting-started.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/getting-started.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- getting-started.xml 24 Jan 2003 19:39:40 -0000 1.1
+++ getting-started.xml 3 Feb 2003 15:43:38 -0000 1.2
@@ -11,14 +11,14 @@
<section>
<title>Introduction</title>
<p>We've worked hard to write complete documentation for all
the
- different parts of avalon. Unfortunately, this means there is
quite
+ different parts of Avalon. Unfortunately, this means there is
quite
a bit of documentation to sort through =)</p>
</section>
<section>
<title>Avalon for Beginners</title>
<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
+ to Avalon that will get you up and running in about two
minutes. You
can find the draft
<link
href="excalibur/tweety/avalon-for-beginners.html">here</link>.</p>
</section>
@@ -28,19 +28,19 @@
<p>Another really neat document is our
<link href="developing/index.html">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>
+ experienced software engineer, you'll definetely appreciate
it.</p>
</section>
<section>
-<title>Other documentation</title>
- <p>All the various subproject contain quite a bit of
documentation
- as well. I'll point you in the direction of the getting started
+<title>Other Documentation</title>
+ <p>All the various sub-projects contain quite a bit of
documentation
+ as well. I'll point you in the direction of the 'Getting
Started'
documentation for each of them.</p>
<section>
<title>Avalon Framework</title>
<p>Both the Avalon for Beginners and the Developing
with Avalon
- paper introduce you to avalon framework. We suggest
you start
+ paper introduce you to Avalon framework. We suggest
you start
with one of these.</p>
</section>
@@ -53,7 +53,7 @@
<section>
<title>Avalon Cornerstone</title>
- <p>Much the same is true for the cornerstone
documentation. We
+ <p>Much the same is true for the Cornerstone
documentation. We
suggest you read the
<link href="cornerstone/index.html">overview</link>,
then
browse the
@@ -64,26 +64,26 @@
<section>
<title>Avalon Phoenix</title>
<p>The
- <link href="phoenix/getting-started.html">Avalon
Phoenix getting started document</link>
- desribes the HelloWorld demo Service demo. Tt will
take you
+ <link href="phoenix/getting-started.html">Avalon
Phoenix Getting Started document</link>
+ describes the HelloWorld Service demo. It will take you
through downloading, installing and then running the
demo step
- by step so it is an easy place tp start</p>
+ by step so it is an easy place to start.</p>
</section>
<section>
<title>Avalon Logkit</title>
- <p>You will most likely not use logkit by itself, but
+ <p>You will most likely not use Logkit by itself, but
rather with Phoenix or another container, so you don't
normally
- need to learn much about logkit. If you are interested
in learning
+ need to learn much about Logkit. If you are interested
in learning
more about it, there's a really good
<link href="logkit/whitepaper.html">whitepaper</link>
- on it (it doesn't have a real 'getting started'
document).</p>
+ on it (it doesn't have a real 'Getting Started'
document).</p>
</section>
<section>
<title>Avalon Applications</title>
<p>The Phoenix documentation takes you through setting
up the
- Demo application; for the others there is no getting
started
+ Demo application; for the others there is no 'Getting
Started'
documentation.</p>
</section>
</section>
@@ -91,7 +91,7 @@
<section>
<title>When you do get lost...</title>
<p>When you get stuck in sources, documentation, and the
mailing list archive,
- post your questions to the user mailing list (information on
it is
+ post your questions to the users mailing list (information on
it is
<link
href="http://jakarta.apache.org/site/mail.html";>here</link>). For
many, Avalon poses a steep learning curve, and we'll try and
help you
flatten it as much as we can.</p>
1.3 +11 -11 jakarta-avalon-site/src/documentation/content/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/index.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.xml 29 Jan 2003 15:11:36 -0000 1.2
+++ index.xml 3 Feb 2003 15:43:38 -0000 1.3
@@ -8,7 +8,7 @@
<section>
<title>Shaping up....</title>
<p>This site is still shaping up. You need to go to
- <link href="http://jakarta.apache.org/avalon/";>the jakarta pages</link>
+ <link href="http://jakarta.apache.org/avalon/";>the Jakarta pages</link>
for now.</p>
</section>
<section>
@@ -39,13 +39,13 @@
<title>Project Goals</title>
<p>
As many people point out, software engineering is a very uncommon procedure
- in software development and even more uncommon in auto-organized open
- source projects. The main goal of this project is to design a way for
+ in software development and even more uncommon in auto-organized Open
+ Source projects. The main goal of this project is to design a way for
different projects to share resources avoiding as much as possible efforts
duplication.
</p>
<p>
- The Avalon Team are proud to announce a new whitepaper that covers how
+ The Avalon Team is proud to announce a new whitepaper that covers how
to develop with Avalon. It covers the Framework, and touches on the
LogKit and Excalibur. You can find
<link
href="http://jakarta.apache.org/avalon/developing/index.html";>Developing with Apache
Avalon</link>
@@ -70,7 +70,7 @@
a collection of code design patterns, rules, guidelines and suggestions
on how to
write software that "plugs" into the framework. The framework does not
impose restrictions on the application that uses it, but rather precious
guidelines to
- help the developers reuse as much work they can from other solutions.
+ help the developers reuse as much work as they can from other solutions.
</p>
</section>
@@ -87,8 +87,8 @@
<title>Phoenix</title>
<p>
<link
href="http://jakarta.apache.org/avalon/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
+ 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
facility.
</p>
@@ -97,7 +97,7 @@
<section>
<title>Cornerstone</title>
<p>
- <link
href="http://jakarta.apache.org/avalon/cornerstone/index.html";>Cornerstone</link> is a
repository.
+ <link
href="http://jakarta.apache.org/avalon/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.
@@ -108,7 +108,7 @@
<title>Applications</title>
<p>
<link
href="http://jakarta.apache.org/avalon/apps/index.html";>Applications</link> is a
repository of
- Phoenix blocks. Some are simple self-contained demos of Phoenix
applications,
+ 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,
then these applications could be good inspiration.
@@ -119,9 +119,9 @@
<title>LogKit</title>
<p>
<link
href="http://jakarta.apache.org/avalon/logkit/index.html";>LogKit</link> is the
preferred logging toolkit
- used by the Avalon subprojects.</p>
+ used by the Avalon sub-projects.</p>
<p>
- It is quite possible to use the other avalon subprojects without committing
to logkit.
+ It is quite possible to use the other avalon sub-projects without committing
to logkit.
We support log4j and JDK 1.4 logging as well.
</p>
</section>
1.2 +5 -5
jakarta-avalon-site/src/documentation/content/xdocs/mailing-lists.xml
Index: mailing-lists.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/mailing-lists.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- mailing-lists.xml 24 Jan 2003 19:39:40 -0000 1.1
+++ mailing-lists.xml 3 Feb 2003 15:43:38 -0000 1.2
@@ -24,7 +24,7 @@
<section>
<title>The lists</title>
<section>
- <title>The Avalon User List</title>
+ <title>The Avalon Users List</title>
<p>
<em>Light Traffic</em>
<link href="mailto:[EMAIL PROTECTED]";>Subscribe</link>
@@ -33,13 +33,13 @@
<link href="nntp://news.gmane.org/gmane.comp.jakarta.avalon.user";>News
gateway</link>
</p>
<p>
- This list is for users that are using Avalon in their own projects to ask
+ This list is for users who are using Avalon in their own projects to ask
questions, share knowledge, and discuss issues related to using the Avalon
suite of software.
</p>
</section>
<section>
- <title>The Avalon Developer List</title>
+ <title>The Avalon Developers List</title>
<p>
<em>Medium Traffic</em>
<link href="mailto:[EMAIL PROTECTED]";>Subscribe</link>
@@ -48,9 +48,9 @@
<link href="nntp://news.gmane.org/gmane.comp.jakarta.avalon.devel";>News
gateway</link>
</p>
<p>
- This list is for developers that are maintaining Avalon or wanting to influence
+ This list is for developers who are maintaining Avalon or wanting to influence
its design to ask questions, share knowledge, and discuss issues related to
developing
- and the Avalon framework.
+ the Avalon framework.
</p>
</section>
<section>
1.2 +2 -2 jakarta-avalon-site/src/documentation/content/xdocs/news.xml
Index: news.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/news.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- news.xml 24 Jan 2003 19:39:40 -0000 1.1
+++ news.xml 3 Feb 2003 15:43:38 -0000 1.2
@@ -16,9 +16,9 @@
<title>Avalon is now a top-level project!</title>
<p>The Apache board has passed a resolution to set up a "top-level" project
- for Avalon. This basically means avalon gets its own PMC made up of the
avalon
+ for Avalon. This basically means Avalon gets its own PMC made up of the
Avalon
committers, reporting directly to the board. The complete text of the
resolution
- that passed on Monday 18 November 2002, which created this project is:</p>
+ that passed on Monday, November 18, 2002, which created this project
is:</p>
<source>
WHEREAS, the Board of Directors deems it to be in
the best interests of the Foundation and consistent with
1.3 +6 -6
jakarta-avalon-site/src/documentation/content/xdocs/components/index.xml
Index: index.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/components/index.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.xml 29 Jan 2003 15:10:44 -0000 1.2
+++ index.xml 3 Feb 2003 15:43:38 -0000 1.3
@@ -8,13 +8,13 @@
<section>
<title>Shaping up....</title>
<p>This site is still shaping up. You need to go to
- <link href="http://jakarta.apache.org/avalon/";>the jakarta pages</link>
+ <link href="http://jakarta.apache.org/avalon/";>the Jakarta pages</link>
for now.</p>
</section>
<section>
<title>Cornerstone</title>
<p>Cornerstone is a repository for reusable services/components/blocks
- for phoenix and other containers with similar features. The subproject
+ for Phoenix and other containers with similar features. The sub-project
website is at
<link
href="http://avalon.apache.org/cornerstone/";>http://avalon.apache.org/cornerstone/</link>.</p>
</section>
@@ -22,14 +22,14 @@
<title>Excalibur</title>
<p>Excalibur is a large repository containing lots of materials, including
the ECM and Fortress containers and container-facilitating code, reusable
- avalon components, and some components not-so-closely coupled to avalon.
The
- subproject website is at
+ Avalon components, and some components not-so-closely coupled to Avalon.
The
+ sub-project website is at
<link
href="http://avalon.apache.org/excalibur/";>http://avalon.apache.org/excalibur/</link>.</p>
</section>
<section>
<title>Logkit</title>
- <p>Logkt is our biggest "reusable component". It's a real cool logging
toolkit.
- The subproject website is at
+ <p>Logkit is our biggest "reusable component". It's a real cool logging
toolkit.
+ The sub-project website is at
<link
href="http://jakarta.apache.org/avalon/logkit/";>http://avalon.apache.org/avalon/logkit/</link>.</p>
</section>
</body>
1.2 +4 -4
jakarta-avalon-site/src/documentation/content/xdocs/history/index.xml
Index: index.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/history/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 29 Jan 2003 15:57:47 -0000 1.1
+++ index.xml 3 Feb 2003 15:43:38 -0000 1.2
@@ -30,15 +30,15 @@
<p>
Over time the Java Apache Server Framework project was renamed Avalon. This was
in
- recognition that the original ideas have evolved over time. Avalon became a
+ recognition that the original ideas had evolved over time. Avalon became a
repository of general utility code, a design and testing ground for component
based
- solutions, a micro kernel and set of generalized server oriented services. This
combined
+ solutions, a micro kernel and set of generalized server oriented services.
This, combined
with a move from the Java Apache project to the Jakarta project prompted the
revision.
At this time the kernel code was repackaged under the name Phoenix, core
services
- under the name Cornerstone and the general components was packaged under name
Excalibur.
+ under the name Cornerstone and the general components were packaged under the
name Excalibur.
</p>
<p>
- You may check the historical changes from before splitting Avalon into separate
projects <link href="changes.html">here</link>.
+ You may check the historical changes from before splitting Avalon into seperate
projects <link href="changes.html">here</link>.
</p>
</section>
1.3 +2 -2
jakarta-avalon-site/src/documentation/content/xdocs/project/book.xml
Index: book.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/project/book.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- book.xml 27 Jan 2003 13:34:37 -0000 1.2
+++ book.xml 3 Feb 2003 15:43:38 -0000 1.3
@@ -11,7 +11,7 @@
<menu-item label="Our Mission" href="../mission.html"/>
<menu-item label="Project History" href="../history/index.html"/>
<menu-item label="Meritocracy"
href="http://jakarta.apache.org/site/decisions.html"/>
- <menu-item label="High esteem"
href="http://dictionary.reference.com/search?q=esteem"/>
+ <menu-item label="High Esteem"
href="http://dictionary.reference.com/search?q=esteem"/>
<menu-item label="The Apache Way"
href="http://nagoya.apache.org/wiki/apachewiki.cgi?ApacheWay"/>
</menu>
@@ -26,6 +26,6 @@
<menu label="Development Process">
<menu-item label="Roadmap" href="roadmap.html"/>
<menu-item label="Release Management" href="releases.html"/>
- <menu-item label="Patches and Bugreports" href="patches.html"/>
+ <menu-item label="Patches and Bug Reports" href="patches.html"/>
</menu>
</book>
1.3 +5 -5
jakarta-avalon-site/src/documentation/content/xdocs/project/patches.xml
Index: patches.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/project/patches.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- patches.xml 29 Jan 2003 15:11:36 -0000 1.2
+++ patches.xml 3 Feb 2003 15:43:38 -0000 1.3
@@ -2,7 +2,7 @@
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
"document-v11.dtd">
<document>
<header>
- <title>Apache Avalon project: Patches and Bugrepors</title>
+ <title>Apache Avalon project: Patches and Bug Reports</title>
</header>
<body>
<section>
@@ -13,9 +13,9 @@
<link
href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Avalon&version=unspecified&rep_platform=all&op_sys=all&[EMAIL PROTECTED]";><strong>Enter
a bug</strong></link><br/>
<br/>
but please make sure the bug you're reporting doesn't exist yet, you
include
- all relevant information, etc etc. See
+ all relevant information, etc. See
<link
href="http://nagoya.apache.org/wiki/apachewiki.cgi?HowDoISubmitUsefulBugReports";>this
page</link>
- for more on how to submit bug reports, or try google.</p>
+ for more on how to submit bug reports, or try Google.</p>
</section>
<section>
<title>Submitting patches</title>
@@ -25,12 +25,12 @@
in a single patch file. Make sure the patch adheres to the coding
standards,
and includes appropriate javadoc.</p>
- <p>When you've built the patch, file a new bug report in bugzilla if one
+ <p>When you've built the patch, file a new bug report in Bugzilla if one
does not exist yet, explain the reason behind the patch, how the patch
fixes
the issues, and add the patch as an attachment.</p>
<p>If your patch is not getting applied or there is no response, start
nagging
- the developers (politely, please :D) on the development mailing list.</p>
+ the developers (politely, please :D) on the developers mailing list.</p>
<section>
<title>Documentation patches</title>
1.2 +9 -9
jakarta-avalon-site/src/documentation/content/xdocs/project/pmc.xml
Index: pmc.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/project/pmc.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- pmc.xml 27 Jan 2003 13:34:37 -0000 1.1
+++ pmc.xml 3 Feb 2003 15:43:38 -0000 1.2
@@ -13,15 +13,15 @@
</section>
<section>
<title>So what is this PMC thing?</title>
- <p>Apache is a legal entity, ie a real non-profit organisation,
- with a charter, members, a board, a president, etc etc. You can
+ <p>Apache is a legal entity, i.e. a real non-profit organisation,
+ with a charter, members, a board, a president, etc. You can
read all about that
<link href="http://www.apache.org/foundation/";>here</link></p>
<p>A PMC, Project Management Committee, is a group of people
- appointed with the task of managing someting that fits with the
- apache software foundation goals. The Avalon PMC, for example,
- is tasked with managing avalon.</p>
+ appointed with the task of managing something that fits with the
+ Apache Software Foundation goals. The Avalon PMC, for example,
+ is tasked with managing Avalon.</p>
</section>
<section>
<title>What, management?! We've already got plenty of those at
work!</title>
@@ -31,7 +31,7 @@
stuff which still requires management.</p>
<p>For example, in order to protect ourselves and our users, all
- software hosted at apache must be properly copyrighted to the ASF,
+ software hosted at Apache must be properly copyrighted to the ASF,
and licensed under the ASF license. This is something the PMC is
responsible for.</p>
@@ -39,18 +39,18 @@
the development work. There's no "bossing around" here. The PMC
exists only to facilitate free software developers in "doing their
thing", just like the ASF exists "to provide organizational, legal,
- and financial support for the Apache open-source software
+ and financial support for the Apache Open Source software
projects".</p>
</section>
<section>
<title>The PMC Chair and Officer of the Foundation</title>
<p>The position of Avalon PMC chair is an important one; the PMC
- chair has special responsibilities and priviledges as detailed in
+ chair has special responsibilities and privileges as detailed in
the ASF bylaws.</p>
</section>
<section>
<title>So, who's on the PMC?</title>
- <p>This information is contained in the avalon STATUS file, and
+ <p>This information is contained in the Avalon STATUS file, and
also <link href="../whoweare.html">on this page</link>.</p>
</section>
</body>
1.3 +2 -2
jakarta-avalon-site/src/documentation/content/xdocs/project/releases.xml
Index: releases.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/project/releases.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- releases.xml 29 Jan 2003 15:11:36 -0000 1.2
+++ releases.xml 3 Feb 2003 15:43:38 -0000 1.3
@@ -15,7 +15,7 @@
<li><link href="http://jakarta.apache.org/site/decisions.html";>Jakarta decision
process</link></li>
<li><link href="http://httpd.apache.org/dev/release.html";>HTTPD release
policy</link></li>
<li><link
href="http://nagoya.apache.org/bugzilla/reports.cgi?product=Avalon&output=most_doomed&links=1&banner=1&quip=0";>Bug
summary</link></li>
-<li><link href="http://cvs.apache.org/~bodewig/mirror.html";>Distribution Mirroring
howto</link></li>
+<li><link href="http://cvs.apache.org/~bodewig/mirror.html";>Distribution Mirroring
HOWTO</link></li>
<li><link href="http://cvs.apache.org/builds/";>Nightly builds</link></li>
<li><link href="http://gump.covalent.net/jars/latest/";>Nightly builds:
jars@covalent</link></li>
<li><link href="http://freshmeat.net/articles/view/392/";>Freshmeat on software
builds</link></li>
@@ -27,7 +27,7 @@
</section>
<section>
<title>Noel's thoughts</title>
- <p>Noel J Bergman wrote to avalon-dev:</p>
+ <p>Noel J. Bergman wrote to avalon-dev:</p>
<source>
Q: "Is the Avalon PMC able to define a coordinated Release of all the A4
modules such that we know that they all work together?"
1.2 +5 -5
jakarta-avalon-site/src/documentation/content/xdocs/project/roadmap.xml
Index: roadmap.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/project/roadmap.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- roadmap.xml 27 Jan 2003 13:34:37 -0000 1.1
+++ roadmap.xml 3 Feb 2003 15:43:38 -0000 1.2
@@ -12,8 +12,8 @@
<source>
Avalon will be focussing container development into two efforts.
- The first one is the creation of Avalon ESCA. To this end, most
- existing avalon container projects will refocus to be part of
+ The first one is the creation of Avalon SECA. To this end, most
+ existing Avalon container projects will refocus to be part of
that goal.
The roadmap for this effort is roughly as follows:
@@ -23,9 +23,9 @@
- Milestone 3: Phoenix Compatible (Codename: Phoenix5)
- Milestone 4: Profileable, pluggable container (Codename: Spearhead)
- The second container development effort is the maintainance of existing
- released efforts with an existing userbase, ie phoenix. This will merge
- into the ESCA effort when there is an ESCA release compatible with
+ The second container development effort is the maintenance of existing
+ released efforts with an existing userbase, i.e. Phoenix. This will merge
+ into the SECA effort when there is an SECA release compatible with
those existing efforts.
====================================================================
1.2 +1 -1
jakarta-avalon-site/src/documentation/content/xdocs/seca/index.xml
Index: index.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-site/src/documentation/content/xdocs/seca/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 24 Jan 2003 16:59:23 -0000 1.1
+++ index.xml 3 Feb 2003 15:43:39 -0000 1.2
@@ -8,7 +8,7 @@
<section>
<title>Shaping up....</title>
<p>This site is still shaping up. You need to go to
- <link href="http://jakarta.apache.org/avalon/";>the jakarta pages</link>
+ <link href="http://jakarta.apache.org/avalon/";>the Jakarta pages</link>
for now.</p>
</section>
</body>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
