[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-site-cvs
Subject:    svn commit: r357295 - /jakarta/site/xdocs/site/packageversioning.xml
From:       martinc () apache ! org
Date:       2005-12-17 5:13:32
Message-ID: 20051217051333.84720.qmail () minotaur ! apache ! org
[Download RAW message or body]

Author: martinc
Date: Fri Dec 16 21:13:28 2005
New Revision: 357295

URL: http://svn.apache.org/viewcvs?rev=357295&view=rev
Log:
Some minor corrections.

Modified:
    jakarta/site/xdocs/site/packageversioning.xml

Modified: jakarta/site/xdocs/site/packageversioning.xml
URL: http://svn.apache.org/viewcvs/jakarta/site/xdocs/site/packageversioning.xml?rev=357295&r1=357294&r2=357295&view=diff
 ==============================================================================
--- jakarta/site/xdocs/site/packageversioning.xml (original)
+++ jakarta/site/xdocs/site/packageversioning.xml Fri Dec 16 21:13:28 2005
@@ -29,7 +29,7 @@
 The <a target="_new" \
href='http://java.sun.com/j2se/1.4/docs/guide/versioning/spec/VersioningSpecification.html'>Java(tm) \
Product Versioning Specification</a> allows users to identify the exact version \
information of a package within a JAR. This is particularly useful when users have a \
number of packages, with version interdependences, from various distributions.   </p>
 <p>
-These four simple steps use ANT to maintain and insert the versioning information, \
so all JARs shipped are correctly versioned. <b>Note:</b> This is just one method, \
and in future releases ANT may have built in mechanisms for this task. +These four \
simple steps use Ant to maintain and insert the versioning information, so all JARs \
shipped are correctly versioned. <b>Note:</b> This is just one method, and in future \
releases Ant may have built in mechanisms for this task.  </p>
 <h3>Step 1: Manually create a template manifest file.</h3>
 <p>Java versioning is implemented by attributes set within the manifest of the \
JAR.</p> @@ -54,10 +54,10 @@
 Save this with your build.xml as a file called <b>manifest.template</b>.
 </p>
 <p>
-<b>Note:</b> The <em>{Apacke Package}</em> ought be manually replaced by the package \
                name, e.g. "log4j" or "Axis"<br/>
-<b>Note:</b> The <em>@version@</em> is a specific keyword used later in ANT \
filtering, and will be dynamically updated. +<b>Note:</b> The <em>{Apache \
Package}</em> ought be manually replaced by the package name, e.g. "log4j" or \
"Axis"<br/> +<b>Note:</b> The <em>@version@</em> is a specific keyword used later in \
Ant filtering, and will be dynamically updated.  </p>
-<h3>Step 2: Maintain the version in your ANT build script</h3>
+<h3>Step 2: Maintain the version in your Ant build script</h3>
 <p>
 Set and maintain the <b>${version}</b> property.
 </p>
@@ -84,7 +84,7 @@
 </p>
 <h3>Step 4: Create your JAR, setting the manifest attribute</h3>
 <p>
-This sets the <b>META-INF/Manifest.mf</b> in the JAR file.
+This sets the <b>META-INF/manifest.mf</b> in the JAR file.
 </p>
 <p>
 <table border="1" align="center">



---------------------------------------------------------------------
To unsubscribe, e-mail: site-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: site-cvs-help@jakarta.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]