kaz 02/03/20 20:09:49
Modified: xdocs build-file.xml getting-started.xml jrcs.xml
metrics.xml musings.xml
Log:
Ran a spell checker on all of the docs ...
Revision Changes Path
1.16 +1 -1 jakarta-turbine-maven/xdocs/build-file.xml
Index: build-file.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/build-file.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- build-file.xml 20 Mar 2002 22:52:52 -0000 1.15
+++ build-file.xml 21 Mar 2002 04:09:48 -0000 1.16
@@ -122,7 +122,7 @@
]]></source>
<p>
It is important to note the use of the <code>maven:start</code>
- and <code>maven:end</code> delimeters. This will enable Maven
+ and <code>maven:end</code> delimiters. This will enable Maven
to be upgraded in a seamless manner in the future.
</p>
<p>
1.7 +4 -4 jakarta-turbine-maven/xdocs/getting-started.xml
Index: getting-started.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/getting-started.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- getting-started.xml 20 Mar 2002 23:19:49 -0000 1.6
+++ getting-started.xml 21 Mar 2002 04:09:48 -0000 1.7
@@ -32,7 +32,7 @@
project, and using Maven. If you are only interested in
building a project that uses Maven, you can probably skip the
second section (integrating Maven) and just jump to the last
- section after you have sucessfully installed Maven. However, it
+ section after you have successfully installed Maven. However, it
is recommended that you read the entire document because it will
provide you with a better understanding of the Maven project.
</p>
@@ -72,7 +72,7 @@
filesystem. Simply, unjar the JAR file in the directory you
want your Maven installation to reside. Note: the JAR has been
packaged with a top-level <code>maven</code> directory for
- convienence.
+ convenience.
</p>
<source><![CDATA[
jar xf maven-install.jar
@@ -326,12 +326,12 @@
You'll notice that all of the code is compiled, and then unit
tested, before it is packaged into a JAR file. The unit tests
generate reports that are later parsed to create an HTML report
- that is part of the generated site documentaion. The JAR file
+ that is part of the generated site documentation. The JAR file
can also be automatically distributed.
</p>
<p>
The biggest bang for you buck right now is the generation of your
- site documenation. Maven will generate documentation that is
+ site documentation. Maven will generate documentation that is
consistent with the rest of the site. This list of documentation
includes: developer lists, mailing lists, dependencies, unit test
reports, source code metrics, change logs, JavaDocs, and
1.6 +3 -3 jakarta-turbine-maven/xdocs/jrcs.xml
Index: jrcs.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/jrcs.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- jrcs.xml 11 Mar 2002 23:43:56 -0000 1.5
+++ jrcs.xml 21 Mar 2002 04:09:48 -0000 1.6
@@ -58,7 +58,7 @@
Both distributions of JRCS contain bare-bones API documentation
generated by JavaDoc. There's also a
<a href="http://www.suigeneris.org/jrcs/doc/api/";>local
- copy</a> of the documentation accesible from this site.
+ copy</a> of the documentation accessible from this site.
</p>
<p>
In the lack of a user manual, I recommend you examine the test
@@ -127,8 +127,8 @@
<td> 2001.09.17 </td>
<td> v0.1.1 </td>
<td>
- Added Archive.getReleaseVersion() methods to retreive tip
- version numbers without having to retreive the the
+ Added Archive.getReleaseVersion() methods to retrieve tip
+ version numbers without having to retrieve the the
release's text.
<p/>
Fixed BranchNode.nextInPathTo() so it went on till the tip
1.8 +2 -2 jakarta-turbine-maven/xdocs/metrics.xml
Index: metrics.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/metrics.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- metrics.xml 5 Mar 2002 14:52:34 -0000 1.7
+++ metrics.xml 21 Mar 2002 04:09:49 -0000 1.8
@@ -16,7 +16,7 @@
some metrics that are of interest in a design.
</p>
<p>
- Most of it has been blatently copied from the <a
+ Most of it has been blatantly copied from the <a
href="http://www.webgain.com";>WebGain</a> QA manual and from
Robert C. Martin article : <a
href="http://www.objectmentor.com/resources/articles/oodmetrc.pdf";>Object
@@ -97,7 +97,7 @@
metric dating from before the rise of structured programming,
and it is still in widespread use today. The size of a method
affects the ease with which it can be understood, its
- reusability and its maintainability. There are a variety of
+ re-usability and its maintainability. There are a variety of
ways that the size can be calculated. These include counting
all the lines of code, the number of statements, the blank
lines of code, the lines of commentary, and the lines
1.14 +4 -4 jakarta-turbine-maven/xdocs/musings.xml
Index: musings.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/musings.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- musings.xml 19 Mar 2002 18:15:30 -0000 1.13
+++ musings.xml 21 Mar 2002 04:09:49 -0000 1.14
@@ -20,7 +20,7 @@
the development of ajc.
</li>
<li>
- possibly incorporate <a
href="http://www.cs.uoregon.edu/research/perpetual/dasada/Software/Gretel/";>Gretel</a>,
looks similiar to quilt.
+ possibly incorporate <a
href="http://www.cs.uoregon.edu/research/perpetual/dasada/Software/Gretel/";>Gretel</a>,
looks similar to quilt.
</li>
<li>
how to easily extend the build system for project specifics, we don't
@@ -45,7 +45,7 @@
the idea we want to stress.
</li>
<li>
- cvs log analyser
+ cvs log analyzer
</li>
<li>
build tool
@@ -60,7 +60,7 @@
source formatter
</li>
<li>
- make something like webgain's Quality Analyser
+ make something like webgain's Quality Analyzer
</li>
<li>
audit
@@ -121,7 +121,7 @@
values. at least make this the default.
. Before warning users about jar that can't be distributed, check to make
sure they don't already have it. (warner's idea)
-. Figure the scenerio where the project must generate sources before
+. Figure the scenario where the project must generate sources before
building. We have some crappy deps in the fulcrum build that need
to be cleaned up.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
