jon 2002/12/17 11:54:56
Modified: docs/site packageversioning.html
xdocs/site packageversioning.xml
Log:
lowercase html tags
added missing title tag
Revision Changes Path
1.10 +64 -64 jakarta-site2/docs/site/packageversioning.html
Index: packageversioning.html
===================================================================
RCS file: /home/cvs/jakarta-site2/docs/site/packageversioning.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- packageversioning.html 12 Dec 2002 07:53:15 -0000 1.9
+++ packageversioning.html 17 Dec 2002 19:54:56 -0000 1.10
@@ -18,7 +18,7 @@
- <title>The Jakarta Site -
$root.getChild("properties").getChild("title").getText()</title>
+ <title>The Jakarta Site - Package versioning</title>
</head>
<body bgcolor="#ffffff" text="#000000" link="#525D76">
@@ -148,85 +148,85 @@
<table
border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
- <a name="Package Versioning"><strong>Package Versioning</strong></a>
+ <a name="Package versioning"><strong>Package versioning</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
- <P>
-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.
-</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>
- <P>
-See Javasoft's documentation on: <A TARGET="_new"
HREF="http://java.sun.com/j2se/1.4/docs/guide/versioning/spec/VersioningSpecification.html#JARManifestFormat";>JAR
Manifest Format</A>
-</P>
- <P>
-<TABLE BORDER="1" ALIGN="CENTER">
-<TR><TD><PRE>
+ <p>
+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.
+</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>
+ <p>
+See Javasoft's documentation on: <a target="_new"
href="http://java.sun.com/j2se/1.4/docs/guide/versioning/spec/VersioningSpecification.html#JARManifestFormat";>JAR
Manifest Format</a>
+</p>
+ <p>
+<table border="1" align="center">
+<tr><td><pre>
Manifest-version: 1.0
Name: org/apache/{Apache Package}/
Implementation-Title: {Apache Package}
Implementation-Version: @version@
Implementation-Vendor: "Apache Software Foundation"
-</PRE>
-</TD></TR>
-</TABLE>
-</P>
- <P>
-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.
-</P>
- <H3>Step 2: Maintain the version in
your ANT build script</H3>
- <P>
-Set and maintain the <B>${version}</B> property.
-</P>
- <P>
-<TABLE BORDER="1" ALIGN="CENTER">
-<TR><TD><PRE><property name="version" value="1-1-1" /></PRE></TD></TR>
-</TABLE>
-</P>
- <H3>Step 3: Create the manifest,
filtering the version</H3>
- <P>
-This replaces <B>@version@</B> in <EM>manifest.template</EM> with <B>1-1-1</B> in
<EM>manifest.mf</EM>.
-</P>
- <P>
-<TABLE BORDER="1" ALIGN="CENTER">
-<TR><TD><PRE>
+</pre>
+</td></tr>
+</table>
+</p>
+ <p>
+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.
+</p>
+ <h3>Step 2: Maintain the version in
your ANT build script</h3>
+ <p>
+Set and maintain the <b>${version}</b> property.
+</p>
+ <p>
+<table border="1" align="center">
+<tr><td><pre><property name="version" value="1-1-1" /></pre></td></tr>
+</table>
+</p>
+ <h3>Step 3: Create the manifest,
filtering the version</h3>
+ <p>
+This replaces <b>@version@</b> in <em>manifest.template</em> with <b>1-1-1</b> in
<em>manifest.mf</em>.
+</p>
+ <p>
+<table border="1" align="center">
+<tr><td><pre>
<target name="manifest">
<filter token="version" value="${version}" />
<copy file="manifest.template"
tofile="manifest.mf"
overwrite="true"
filtering="true" />
-</target></PRE></TD></TR>
-</TABLE>
-</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.
-</P>
- <P>
-<TABLE BORDER="1" ALIGN="CENTER">
-<TR><TD><PRE>
-<target name="distribution" depends="<EM>...</EM> manifest <EM>...</EM>">
- <jar jarfile=<EM>...</EM>
- <B>manifest="manifest.mf"</B>/>
-</PRE>
-</TD></TR>
-</TABLE>
-</P>
- <HR WIDTH="100%" />
- <P>
-Sample Files: <A
HREF="packageversioning-manifest.template">manifest.template</A>, <A
HREF="packageversioning-build.xml">build.xml</A>
-</P>
+</target></pre></td></tr>
+</table>
+</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.
+</p>
+ <p>
+<table border="1" align="center">
+<tr><td><pre>
+<target name="distribution" depends="<em>...</em> manifest <em>...</em>">
+ <jar jarfile=<em>...</em>
+ <b>manifest="manifest.mf"</b>/>
+</pre>
+</td></tr>
+</table>
+</p>
+ <hr width="100%" />
+ <p>
+Sample Files: <a
href="packageversioning-manifest.template">manifest.template</a>, <a
href="packageversioning-build.xml">build.xml</a>
+</p>
</blockquote>
</p>
</td></tr>
1.3 +64 -63 jakarta-site2/xdocs/site/packageversioning.xml
Index: packageversioning.xml
===================================================================
RCS file: /home/cvs/jakarta-site2/xdocs/site/packageversioning.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- packageversioning.xml 1 Apr 2002 15:47:53 -0000 1.2
+++ packageversioning.xml 17 Dec 2002 19:54:56 -0000 1.3
@@ -3,87 +3,88 @@
<properties>
<author email="[EMAIL PROTECTED]">ajack</author>
+ <title>Package versioning</title>
</properties>
<body>
-<section name="Package Versioning">
+<section name="Package versioning">
-<P>
-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.
-</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>
-<P>
-See Javasoft's documentation on: <A TARGET="_new"
HREF='http://java.sun.com/j2se/1.4/docs/guide/versioning/spec/VersioningSpecification.html#JARManifestFormat'>JAR
Manifest Format</A>
-</P>
-<P>
-<TABLE BORDER="1" ALIGN="CENTER">
-<TR><TD><PRE>
+<p>
+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.
+</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>
+<p>
+See Javasoft's documentation on: <a target="_new"
href='http://java.sun.com/j2se/1.4/docs/guide/versioning/spec/VersioningSpecification.html#JARManifestFormat'>JAR
Manifest Format</a>
+</p>
+<p>
+<table border="1" align="center">
+<tr><td><pre>
Manifest-version: 1.0
Name: org/apache/{Apache Package}/
Implementation-Title: {Apache Package}
Implementation-Version: @version@
Implementation-Vendor: "Apache Software Foundation"
-</PRE>
-</TD></TR>
-</TABLE>
-</P>
-<P>
-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.
-</P>
-<H3>Step 2: Maintain the version in your ANT build script</H3>
-<P>
-Set and maintain the <B>${version}</B> property.
-</P>
-<P>
-<TABLE BORDER="1" ALIGN="CENTER">
-<TR><TD><PRE><property name="version" value="1-1-1"
/></PRE></TD></TR>
-</TABLE>
-</P>
-<H3>Step 3: Create the manifest, filtering the version</H3>
-<P>
-This replaces <B>@version@</B> in <EM>manifest.template</EM> with <B>1-1-1</B> in
<EM>manifest.mf</EM>.
-</P>
-<P>
-<TABLE BORDER="1" ALIGN="CENTER">
-<TR><TD><PRE>
+</pre>
+</td></tr>
+</table>
+</p>
+<p>
+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.
+</p>
+<h3>Step 2: Maintain the version in your ANT build script</h3>
+<p>
+Set and maintain the <b>${version}</b> property.
+</p>
+<p>
+<table border="1" align="center">
+<tr><td><pre><property name="version" value="1-1-1"
/></pre></td></tr>
+</table>
+</p>
+<h3>Step 3: Create the manifest, filtering the version</h3>
+<p>
+This replaces <b>@version@</b> in <em>manifest.template</em> with <b>1-1-1</b> in
<em>manifest.mf</em>.
+</p>
+<p>
+<table border="1" align="center">
+<tr><td><pre>
<target name="manifest">
<filter token="version" value="${version}" />
<copy file="manifest.template"
tofile="manifest.mf"
overwrite="true"
filtering="true" />
-</target></PRE></TD></TR>
-</TABLE>
-</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.
-</P>
-<P>
-<TABLE BORDER="1" ALIGN="CENTER">
-<TR><TD><PRE>
-<target name="distribution" depends="<EM>...</EM> manifest <EM>...</EM>">
- <jar jarfile=<EM>...</EM>
- <B>manifest="manifest.mf"</B>/>
-</PRE>
-</TD></TR>
-</TABLE>
-</P>
-<HR WIDTH="100%"/>
-<P>
-Sample Files: <A
HREF="packageversioning-manifest.template">manifest.template</A>, <A
HREF="packageversioning-build.xml">build.xml</A>
-</P>
+</target></pre></td></tr>
+</table>
+</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.
+</p>
+<p>
+<table border="1" align="center">
+<tr><td><pre>
+<target name="distribution" depends="<em>...</em> manifest <em>...</em>">
+ <jar jarfile=<em>...</em>
+ <b>manifest="manifest.mf"</b>/>
+</pre>
+</td></tr>
+</table>
+</p>
+<hr width="100%" />
+<p>
+Sample Files: <a
href="packageversioning-manifest.template">manifest.template</a>, <a
href="packageversioning-build.xml">build.xml</a>
+</p>
</section>
</body>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
