You are viewing a plain text version of this content. The canonical link for it is here.
Posted to alexandria-dev@jakarta.apache.org by ru...@apache.org on 2001/10/20 22:50:33 UTC
cvs commit: jakarta-alexandria/proposal/gump/stylesheet bash.xsl build.xsl update.xsl win2k.xsl
rubys 01/10/20 13:50:33
Modified: proposal/gump/project xml-xalan.xml
proposal/gump/site/xdocs project.xml workspace.xml
proposal/gump/site/xdocs/stylesheets project.xml
proposal/gump/stylesheet bash.xsl build.xsl update.xsl
win2k.xsl
Added: proposal/gump/site/xdocs usage.xml
Log:
Add xalan to the bootclasspath
Revision Changes Path
1.22 +2 -2 jakarta-alexandria/proposal/gump/project/xml-xalan.xml
Index: xml-xalan.xml
===================================================================
RCS file: /home/cvs/jakarta-alexandria/proposal/gump/project/xml-xalan.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- xml-xalan.xml 2001/10/13 12:54:26 1.21
+++ xml-xalan.xml 2001/10/20 20:50:33 1.22
@@ -14,7 +14,7 @@
<depend project="xml-xerces"/>
<home nested="java/build"/>
- <jar name="xalan.jar" id="xalan"/>
+ <jar name="xalan.jar" id="xalan" type="boot"/>
</project>
<project name="xml-xalan1-compat">
@@ -56,7 +56,7 @@
<work nested="java/build/classes"/>
<home nested="java/build/xalan-j_gump"/>
- <jar name="bin/xalan.jar"/>
+ <jar name="bin/xalan.jar" type="boot"/>
</project>
<project name="xml-xalan2-smoketest">
1.3 +225 -218 jakarta-alexandria/proposal/gump/site/xdocs/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/jakarta-alexandria/proposal/gump/site/xdocs/project.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- project.xml 2001/09/25 22:35:36 1.2
+++ project.xml 2001/10/20 20:50:33 1.3
@@ -1,218 +1,225 @@
-<?xml version="1.0"?>
-<document>
-
- <properties>
- <author email="rubys@us.ibm.com">Sam Ruby</author>
- <title>Gump</title>
- </properties>
-
-<body>
-
- <section name="project">
- <p>A project is the atomic unit of integration. It can describe an
- installable package or a buildable product. The nested elements of
- a project definition fall into three different "groups", each optional:</p>
-
- <ul>
- <li>Build instructions: <ant> and <script>. Describes how to
- produce the outputs from the inputs.</li>
- <li>Inputs: <depend>, <option>, and <work>. Describes
- where to find the inputs (primarily jar files, but can be directories and
- files).</li>
- <li>Outputs: <home> and <jar>. Describes where to locate
- the output files.</li>
- </ul>
-
- <p>Note that <depend> elements nested within <ant>
- elements are precisely equivalent to specifying both a property to be
- passed to Ant, as well as a separate depend element.</p>
-
- <subsection name="ant">
- <p>Identifies this project as "buildable", and specifies the
- target to build and the properties to be passed to ant. The full
- description of this XML element can be found
- <a href="ant.html">here</a></p>
-
- <p><a href="http://jakarta.apache.org/ant/">Jakarta Ant</a> is the
- defacto build tool used by a large number of Open Source Java
- projects.</p>
- </subsection>
-
- <subsection name="script">
- <p>Identifies this project as "buildable", and specifies the
- script to be executed in order to make this happen. The assumption
- is that the script can be invoked in a platform independent manner,
- though the contents of the script may be platform specific.
- Specifically, if the name of the script is "name", it will be
- invoked as follows:</p>
-
- <p>At the present time, the only use of this is during the bootstrap
- process for Ant.</p>
-
- <ul>
- <li>On Windows/batch, "call .\name.bat"</li>
- <li>On Unix/bash, "./name.sh"</li>
- </ul>
-
- <table>
- <tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required?</th>
- </tr>
- <tr>
- <td>name</td>
- <td>The name of the script to execute.</td>
- <td>Yes</td>
- </tr>
- </table>
- </subsection>
-
- <subsection name="depend">
- <p>Specifies the name of a required prerequisite project. If a
- definition for that project is not found in the workspace, the
- generation will fail.</p>
-
- <p>For a build "all", the invocation of ant or the script is bypassed
- if any of the outputs of the specified project can not be found.</p>
-
- <p>For both script and ant based builds, any jars defined by the
- specified project as outputs are added to the CLASSPATH prior to
- invoking the build operation.</p>
-
- <table>
- <tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required?</th>
- </tr>
- <tr>
- <td>project</td>
- <td>The name of the project depended on.</td>
- <td>Yes</td>
- </tr>
- </table>
- </subsection>
-
- <subsection name="option">
- <p>Specifies the name of an optional prerequisite project. If a
- definition for that project is not found in the workspace, the
- dependency is ignored.</p>
-
- <p>For both script and ant based builds, any jars defined by the
- specified project as outputs are added to the CLASSPATH prior to
- invoking the build operation. If the files are not present,
- this will have little effect.</p>
-
- <table>
- <tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required?</th>
- </tr>
- <tr>
- <td>project</td>
- <td>The name of the project depended on.</td>
- <td>Yes</td>
- </tr>
- </table>
- </subsection>
-
- <subsection name="work">
- <p>Adds a directory or a file to the class path. This is to allow
- projects which have compilation dependencies on byproducts of the build
- (example: tests which import the project itself. This is necessary when
- using the Ant build.sysclasspath="ignore".</p>
-
- <p>It generally is OK if the directory is not present prior to the
- build. However, if this directory is deleted during the course of
- the build, the behavior of the JVM may become unpredictable.</p>
-
- <p>If neither the parent nor the nested attributes are present, then
- the srcdir for the module is added to the classpath.</p>
-
- <table>
- <tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required?</th>
- </tr>
- <tr>
- <td>parent</td>
- <td>Name of a directory or file, relative to the base directory
- of the workspace.</td>
- <td>No</td>
- </tr>
- <tr>
- <td>nested</td>
- <td>Name of a directory or file, relative to the srcdir of the module
- containing this project.</td>
- <td>No</td>
- </tr>
- </table>
- </subsection>
-
- <subsection name="home">
- <p>The home directory for a project is the directory which contains the
- files referenceable by another project. In many cases, it is possible
- for another project element by the same name (see the
- <a href="overview.html">overview</a>) to extend a project definition
- for an installable package in such a way that the result actually builds
- the project.</p>
-
- <p>A home attribute on a project definition will override this value.</p>
-
- <p>A package attribute on a project will provide a default for this
- value. Such a default would be relative to the workspace pkgdir</p>
-
- <p>If none of these attributes or elements, the default value is
- the srcdir for the module.</p>
-
- <table>
- <tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required?</th>
- </tr>
- <tr>
- <td>parent</td>
- <td>Name of a directory or file, relative to the base directory
- of the workspace.</td>
- <td>No</td>
- </tr>
- <tr>
- <td>nested</td>
- <td>Name of a directory or file, relative to the srcdir of the module
- containing this project.</td>
- <td>No</td>
- </tr>
- </table>
- </subsection>
-
- <subsection name="jar">
- <p>The name of an output jar, relative to the home directory.</p>
-
- <table>
- <tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required?</th>
- </tr>
- <tr>
- <td>name</td>
- <td>The name of the jar</td>
- <td>Yes</td>
- </tr>
- <tr>
- <td>id</td>
- <td>Provides a unique id which can be used to provide selection
- between multiple jars definitions.</td>
- <td>No</td>
- </tr>
- </table>
- </subsection>
-
- </section>
-</body>
-</document>
-
+<?xml version="1.0"?>
+<document>
+
+ <properties>
+ <author email="rubys@us.ibm.com">Sam Ruby</author>
+ <title>Gump</title>
+ </properties>
+
+<body>
+
+ <section name="project">
+ <p>A project is the atomic unit of integration. It can describe an
+ installable package or a buildable product. The nested elements of
+ a project definition fall into three different "groups", each optional:</p>
+
+ <ul>
+ <li>Build instructions: <ant> and <script>. Describes how to
+ produce the outputs from the inputs.</li>
+ <li>Inputs: <depend>, <option>, and <work>. Describes
+ where to find the inputs (primarily jar files, but can be directories and
+ files).</li>
+ <li>Outputs: <home> and <jar>. Describes where to locate
+ the output files.</li>
+ </ul>
+
+ <p>Note that <depend> elements nested within <ant>
+ elements are precisely equivalent to specifying both a property to be
+ passed to Ant, as well as a separate depend element.</p>
+
+ <subsection name="ant">
+ <p>Identifies this project as "buildable", and specifies the
+ target to build and the properties to be passed to ant. The full
+ description of this XML element can be found
+ <a href="ant.html">here</a></p>
+
+ <p><a href="http://jakarta.apache.org/ant/">Jakarta Ant</a> is the
+ defacto build tool used by a large number of Open Source Java
+ projects.</p>
+ </subsection>
+
+ <subsection name="script">
+ <p>Identifies this project as "buildable", and specifies the
+ script to be executed in order to make this happen. The assumption
+ is that the script can be invoked in a platform independent manner,
+ though the contents of the script may be platform specific.
+ Specifically, if the name of the script is "name", it will be
+ invoked as follows:</p>
+
+ <p>At the present time, the only use of this is during the bootstrap
+ process for Ant.</p>
+
+ <ul>
+ <li>On Windows/batch, "call .\name.bat"</li>
+ <li>On Unix/bash, "./name.sh"</li>
+ </ul>
+
+ <table>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required?</th>
+ </tr>
+ <tr>
+ <td>name</td>
+ <td>The name of the script to execute.</td>
+ <td>Yes</td>
+ </tr>
+ </table>
+ </subsection>
+
+ <subsection name="depend">
+ <p>Specifies the name of a required prerequisite project. If a
+ definition for that project is not found in the workspace, the
+ generation will fail.</p>
+
+ <p>For a build "all", the invocation of ant or the script is bypassed
+ if any of the outputs of the specified project can not be found.</p>
+
+ <p>For both script and ant based builds, any jars defined by the
+ specified project as outputs are added to the CLASSPATH prior to
+ invoking the build operation.</p>
+
+ <table>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required?</th>
+ </tr>
+ <tr>
+ <td>project</td>
+ <td>The name of the project depended on.</td>
+ <td>Yes</td>
+ </tr>
+ </table>
+ </subsection>
+
+ <subsection name="option">
+ <p>Specifies the name of an optional prerequisite project. If a
+ definition for that project is not found in the workspace, the
+ dependency is ignored.</p>
+
+ <p>For both script and ant based builds, any jars defined by the
+ specified project as outputs are added to the CLASSPATH prior to
+ invoking the build operation. If the files are not present,
+ this will have little effect.</p>
+
+ <table>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required?</th>
+ </tr>
+ <tr>
+ <td>project</td>
+ <td>The name of the project depended on.</td>
+ <td>Yes</td>
+ </tr>
+ </table>
+ </subsection>
+
+ <subsection name="work">
+ <p>Adds a directory or a file to the class path. This is to allow
+ projects which have compilation dependencies on byproducts of the build
+ (example: tests which import the project itself. This is necessary when
+ using the Ant build.sysclasspath="ignore".</p>
+
+ <p>It generally is OK if the directory is not present prior to the
+ build. However, if this directory is deleted during the course of
+ the build, the behavior of the JVM may become unpredictable.</p>
+
+ <p>If neither the parent nor the nested attributes are present, then
+ the srcdir for the module is added to the classpath.</p>
+
+ <table>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required?</th>
+ </tr>
+ <tr>
+ <td>parent</td>
+ <td>Name of a directory or file, relative to the base directory
+ of the workspace.</td>
+ <td>No</td>
+ </tr>
+ <tr>
+ <td>nested</td>
+ <td>Name of a directory or file, relative to the srcdir of the module
+ containing this project.</td>
+ <td>No</td>
+ </tr>
+ </table>
+ </subsection>
+
+ <subsection name="home">
+ <p>The home directory for a project is the directory which contains the
+ files referenceable by another project. In many cases, it is possible
+ for another project element by the same name (see the
+ <a href="overview.html">overview</a>) to extend a project definition
+ for an installable package in such a way that the result actually builds
+ the project.</p>
+
+ <p>A home attribute on a project definition will override this value.</p>
+
+ <p>A package attribute on a project will provide a default for this
+ value. Such a default would be relative to the workspace pkgdir</p>
+
+ <p>If none of these attributes or elements, the default value is
+ the srcdir for the module.</p>
+
+ <table>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required?</th>
+ </tr>
+ <tr>
+ <td>parent</td>
+ <td>Name of a directory or file, relative to the base directory
+ of the workspace.</td>
+ <td>No</td>
+ </tr>
+ <tr>
+ <td>nested</td>
+ <td>Name of a directory or file, relative to the srcdir of the module
+ containing this project.</td>
+ <td>No</td>
+ </tr>
+ </table>
+ </subsection>
+
+ <subsection name="jar">
+ <p>The name of an output jar, relative to the home directory.</p>
+
+ <table>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required?</th>
+ </tr>
+ <tr>
+ <td>name</td>
+ <td>The name of the jar</td>
+ <td>Yes</td>
+ </tr>
+ <tr>
+ <td>id</td>
+ <td>Provides a unique id which can be used to provide selection
+ between multiple jars definitions.</td>
+ <td>No</td>
+ </tr>
+ <tr>
+ <td>type</td>
+ <td>If the value of this attribute is "boot" then the jar is
+ prepended to the bootclasspath instead of being appended to the
+ classpath.</td>
+ <td>No</td>
+ </tr>
+ </table>
+ </subsection>
+
+ </section>
+</body>
+</document>
+
1.4 +209 -198 jakarta-alexandria/proposal/gump/site/xdocs/workspace.xml
Index: workspace.xml
===================================================================
RCS file: /home/cvs/jakarta-alexandria/proposal/gump/site/xdocs/workspace.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- workspace.xml 2001/09/25 22:35:36 1.3
+++ workspace.xml 2001/10/20 20:50:33 1.4
@@ -1,198 +1,209 @@
-<?xml version="1.0"?>
-<document>
-
- <properties>
- <author email="rubys@us.ibm.com">Sam Ruby</author>
- <title>Gump</title>
- </properties>
-
-<body>
-
- <section name="workspace">
- <p>This represents the combination of projects (either referenced
- directly or indirectly, via profiles) that are to be built together.
- By default, workspaces are named after the hostname of the computer
- which you are building on.</p>
-
- <table>
- <tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required?</th>
- </tr>
- <tr>
- <td>basedir</td>
- <td>Fully qualified directory into which all projects will be
- extracted built.
- </td>
- <td>No</td>
- </tr>
- <tr>
- <td>pkgdir</td>
- <td>Default directory in which to find projects which are installed
- as packages instead of being built. Examples being various jars
- which can be downloaded from Sun's web site.
- </td>
- <td>No</td>
- </tr>
- <tr>
- <td>cvsdir</td>
- <td>Workarea for cvs extracts. The generated update script will
- do the cvs checkouts or updates into this directory. The generated
- build script will copy the results into the basedir prior to
- building.
- </td>
- <td>No. Defaults to ${basedir}/cvs</td>
- </tr>
- <tr>
- <td>logdir</td>
- <td>Directory into which the generated html logs are placed.</td>
- <td>No. Defaults to ${basedir}/log</td>
- </tr>
- <tr>
- <td>version</td>
- <td>Which version of the Gump dtd this workspace was defined against.
- The current version is "0.3".
- </td>
- <td>Yes</td>
- </tr>
- </table>
- <p/>
-
- <subsection name="property">
- <p>Global properties which are to be applied to every Ant execution.
- Commonly used to specify the "build.sysclasspath" property which
- tells Ant how to deal with classpaths specified inside the build.xml
- files</p>
-
- <table>
- <tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required?</th>
- </tr>
- <tr>
- <td>name</td>
- <td>Name of the property to set.</td>
- <td>Yes</td>
- </tr>
- <tr>
- <td>value</td>
- <td>Desired value</td>
- <td>Yes</td>
- </tr>
- </table>
- </subsection>
-
- <subsection name="profile">
- <p>Collections of projects and repositories. While a complete
- profile can be defined here, typically one is referenced via
- href. For a complete description, see the documentation for
- <a href="profile.html">profile</a>.</p>
-
- <table>
- <tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required?</th>
- </tr>
- <tr>
- <td>href</td>
- <td>URI of the file containing the profile definition</td>
- <td>Yes</td>
- </tr>
- </table>
- </subsection>
-
- <subsection name="module">
- <p>An individual module to be included. While a complete
- module can be defined here, typically one is referenced via
- href. For a complete description, see the documentation for
- <a href="module.html">module</a>.</p>
-
- <table>
- <tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required?</th>
- </tr>
- <tr>
- <td>href</td>
- <td>URI of the file containing the module definition</td>
- <td>Yes</td>
- </tr>
- </table>
- </subsection>
-
- <subsection name="project">
- <p>An individual project to be included. While a complete
- project can be defined here, typically one is referenced via
- href. For a complete description, see the documentation for
- <a href="project.html">project</a>.</p>
-
- <table>
- <tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required?</th>
- </tr>
- <tr>
- <td>name</td>
- <td>Name of the project to be modified</td>
- <td>Yes</td>
- </tr>
- <tr>
- <td>home</td>
- <td>Convenient way to specify an override for a root/home
- element.
- </td>
- <td>No</td>
- </tr>
- </table>
- </subsection>
-
- <subsection name="repository">
- <p>An repository from which one or more modules may be obtained
- While a complete repository can be defined here, typically one is
- referenced via href. For a complete description, see the documentation
- for <a href="repository.html">repository</a>.</p>
-
- <table>
- <tr>
- <th>Attribute</th>
- <th>Description</th>
- <th>Required?</th>
- </tr>
- <tr>
- <td>href</td>
- <td>URI of the file containing the repository definition</td>
- <td>Yes</td>
- </tr>
- <tr>
- <td>method</td>
- <td>Convenient way to specify an override for a root/method
- element
- </td>
- <td>No</td>
- </tr>
- <tr>
- <td>user</td>
- <td>Convenient way to specify an override for a root/user
- element
- </td>
- <td>No</td>
- </tr>
- <tr>
- <td>path</td>
- <td>Convenient way to specify an override for a root/path
- element
- </td>
- <td>No</td>
- </tr>
- </table>
- </subsection>
-
- </section>
-</body>
-</document>
-
+<?xml version="1.0"?>
+<document>
+
+ <properties>
+ <author email="rubys@us.ibm.com">Sam Ruby</author>
+ <title>Gump</title>
+ </properties>
+
+<body>
+
+ <section name="workspace">
+ <p>This represents the combination of projects (either referenced
+ directly or indirectly, via profiles) that are to be built together.
+ By default, workspaces are named after the hostname of the computer
+ which you are building on.</p>
+
+ <table>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required?</th>
+ </tr>
+ <tr>
+ <td>basedir</td>
+ <td>Fully qualified directory into which all projects will be
+ extracted built.
+ </td>
+ <td>No</td>
+ </tr>
+ <tr>
+ <td>pkgdir</td>
+ <td>Default directory in which to find projects which are installed
+ as packages instead of being built. Examples being various jars
+ which can be downloaded from Sun's web site.
+ </td>
+ <td>No</td>
+ </tr>
+ <tr>
+ <td>cvsdir</td>
+ <td>Workarea for cvs extracts. The generated update script will
+ do the cvs checkouts or updates into this directory. The generated
+ build script will copy the results into the basedir prior to
+ building.
+ </td>
+ <td>No. Defaults to ${basedir}/cvs</td>
+ </tr>
+ <tr>
+ <td>logdir</td>
+ <td>Directory into which the generated html logs are placed.</td>
+ <td>No. Defaults to ${basedir}/log</td>
+ </tr>
+ <tr>
+ <td>version</td>
+ <td>Which version of the Gump dtd this workspace was defined against.
+ The current version is "0.3".
+ </td>
+ <td>Yes</td>
+ </tr>
+ <tr>
+ <td>sync</td>
+ <td>The name of the command, along with any desired parameters, used to
+ syncronize the build directory with the cvs directory. This can make
+ a <em>considerable</em> performance advantage over the default action
+ which is to recursively remove the directory and copy the entire
+ directory tree. Recommended value for this parameter is
+ <code>"rsync -r -a --delete"</code>.
+ </td>
+ <td>No</td>
+ </tr>
+ </table>
+ <p/>
+
+ <subsection name="property">
+ <p>Global properties which are to be applied to every Ant execution.
+ Commonly used to specify the "build.sysclasspath" property which
+ tells Ant how to deal with classpaths specified inside the build.xml
+ files</p>
+
+ <table>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required?</th>
+ </tr>
+ <tr>
+ <td>name</td>
+ <td>Name of the property to set.</td>
+ <td>Yes</td>
+ </tr>
+ <tr>
+ <td>value</td>
+ <td>Desired value</td>
+ <td>Yes</td>
+ </tr>
+ </table>
+ </subsection>
+
+ <subsection name="profile">
+ <p>Collections of projects and repositories. While a complete
+ profile can be defined here, typically one is referenced via
+ href. For a complete description, see the documentation for
+ <a href="profile.html">profile</a>.</p>
+
+ <table>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required?</th>
+ </tr>
+ <tr>
+ <td>href</td>
+ <td>URI of the file containing the profile definition</td>
+ <td>Yes</td>
+ </tr>
+ </table>
+ </subsection>
+
+ <subsection name="module">
+ <p>An individual module to be included. While a complete
+ module can be defined here, typically one is referenced via
+ href. For a complete description, see the documentation for
+ <a href="module.html">module</a>.</p>
+
+ <table>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required?</th>
+ </tr>
+ <tr>
+ <td>href</td>
+ <td>URI of the file containing the module definition</td>
+ <td>Yes</td>
+ </tr>
+ </table>
+ </subsection>
+
+ <subsection name="project">
+ <p>An individual project to be included. While a complete
+ project can be defined here, typically one is referenced via
+ href. For a complete description, see the documentation for
+ <a href="project.html">project</a>.</p>
+
+ <table>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required?</th>
+ </tr>
+ <tr>
+ <td>name</td>
+ <td>Name of the project to be modified</td>
+ <td>Yes</td>
+ </tr>
+ <tr>
+ <td>home</td>
+ <td>Convenient way to specify an override for a root/home
+ element.
+ </td>
+ <td>No</td>
+ </tr>
+ </table>
+ </subsection>
+
+ <subsection name="repository">
+ <p>An repository from which one or more modules may be obtained
+ While a complete repository can be defined here, typically one is
+ referenced via href. For a complete description, see the documentation
+ for <a href="repository.html">repository</a>.</p>
+
+ <table>
+ <tr>
+ <th>Attribute</th>
+ <th>Description</th>
+ <th>Required?</th>
+ </tr>
+ <tr>
+ <td>href</td>
+ <td>URI of the file containing the repository definition</td>
+ <td>Yes</td>
+ </tr>
+ <tr>
+ <td>method</td>
+ <td>Convenient way to specify an override for a root/method
+ element
+ </td>
+ <td>No</td>
+ </tr>
+ <tr>
+ <td>user</td>
+ <td>Convenient way to specify an override for a root/user
+ element
+ </td>
+ <td>No</td>
+ </tr>
+ <tr>
+ <td>path</td>
+ <td>Convenient way to specify an override for a root/path
+ element
+ </td>
+ <td>No</td>
+ </tr>
+ </table>
+ </subsection>
+
+ </section>
+</body>
+</document>
+
1.1 jakarta-alexandria/proposal/gump/site/xdocs/usage.xml
Index: usage.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<author email="rubys@us.ibm.com">Sam Ruby</author>
<title>Gump</title>
</properties>
<body>
<section name="Building projects for yourself using Gump">
<subsection name="Planning">
<p>The bare minimum required to get started is a JDK, a JAXP 1.1
compliant parser, a command prompt (bash or Windows NT/2K), and Perl.
Perl is only used at the moment for some of the publishing and
notification, so it can be omitted.</p>
<p>It is hightly recommended at this point that you review the
description of the data definitions used by Gump, starting with
the <a href="overview.html">overview</a>.</p>
<p>It also would be useful to gather up a list of installed packages
that you will be referencing in your build. A list of some of the
packages you might want can be found
<a href="http://jakarta.apache.org/builds/gump/latest/packages.html">
here</a>.</p>
</subsection>
<subsection name="Getting the source to Gump">
<source>
export CVSROOT=:pserver:anoncvs@cvs.apache.org:/home/cvspublic
cvs login
cvs co -d gump jakarta-alexandria/proposal/gump</source>
<p>If prompted for the password, enter <b><tt>anoncvs</tt></b></p>
</subsection>
<subsection name="Defining your workspace">
<p>Two sample workspaces are provided, rubix and rubypad. Find the
one that is closest to your needs and make a copy of it. The suggested
name for the file you create is your host name.</p>
<p>Again, reference the <a href="overview.html">overview</a> to see
how you can add projects, define your own profiles, and the modify
which version of referenced projects you want to build.</p>
<p>You will also need to directly modify the <code>gen.bat</code>
or <code>gen.sh</code> scripts to specify where to find the JAXP
implementation to use. At the present time, recent releases of
Xalan are recommended for performance reasons; but the JAXP
reference implementation will likely catch up shortly.</p>
<p><b>Note:</b> Yes, it is tacky that you should have to modify this
file directly. Patches are welcome. Meanwhile, cvs does a farily
good job of merging changes.</p>
</subsection>
<subsection name="Generation">
<p>For Unix and cygwin installations using bash:</p>
<xmp>
bash ./gen.sh
</xmp>
<p>For Windows NT and 2K installations:</p>
<xmp>
gen
</xmp>
<p>This process generates the update and build scripts used in
subsequent steps. It also logs you onto any :pserver: cvs
repository defined which you are not currently logged onto, and
generates the various cross reference pages.</p>
</subsection>
<subsection name="Update">
<p>For Unix and cygwin installations using bash:</p>
<xmp>
bash ./update.sh ( all | module ... )
</xmp>
<p>For Windows NT and 2K installations:</p>
<xmp>
update ( all | module ... )
</xmp>
<p>With this command you can specify you either want to update all or a
specified list or modules. If the module had not been previously
checked out (or the target cvs directory has been removed) then a
checkout is done instead. If <code>all</code> is spacified then a
web page containing the logs for each update is produced, as well as
a summary page. If specific modules are listed, then the output comes
to the screen.</p>
</subsection>
<subsection name="Build">
<p>For Unix and cygwin installations using bash:</p>
<xmp>
bash ./build.sh ( all | clean | (project [ target ... ] ) )
</xmp>
<p>For Windows NT and 2K installations:</p>
<xmp>
build ( all | clean | (project [ target ... ] ) )
</xmp>
<p>With this command you can specify you either want to build all or a
specified project. If <code>all</code> is spacified then a
web page containing the logs for each build is produced, as well as
a summary page. If <code>clean</code> is specified then the only
action that is performed is to syncronize the build directories from
the cvs directories. If a project is specified, then the output comes
to the screen, using the target you provide.</p>
</subsection>
</section>
</body>
</document>
1.6 +13 -36 jakarta-alexandria/proposal/gump/site/xdocs/stylesheets/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/jakarta-alexandria/proposal/gump/site/xdocs/stylesheets/project.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- project.xml 2001/10/05 00:15:39 1.5
+++ project.xml 2001/10/20 20:50:33 1.6
@@ -14,43 +14,9 @@
href="/status.html"/>
<item name="Source"
href="http://cvs.apache.org/viewcvs/jakarta-alexandria/proposal/gump/"/>
+ <item name="Usage"
+ href="/usage.html"/>
</menu>
-
- <menu name="Data Definitions">
- <item name="overview"
- href="/overview.html"/>
- <item name="workspace"
- href="/workspace.html"/>
- <item name="profile"
- href="/profile.html"/>
- <item name="repository"
- href="/repository.html"/>
- <item name="module"
- href="/module.html"/>
- <item name="project"
- href="/project.html"/>
- </menu>
-
- <menu name="Sources">
- <item name="dbxml"
- href="http://www.dbxml.org/"/>
- <item name="devworks"
- href="http://oss.software.ibm.com/developerworks/opensource/"/>
- <item name="exolab"
- href="http://www.exolab.org/"/>
- <item name="jakarta"
- href="http://jakarta.apache.org/"/>
- <item name="jdom"
- href="http://www.jdom.org/"/>
- <item name="mozilla"
- href="http://www.mozilla.org/"/>
- <item name="sourceforge"
- href="http://sourceforge.net/"/>
- <item name="whichever"
- href="http://share.whichever.com/"/>
- <item name="xml"
- href="http://xml.apache.org/"/>
- </menu>
<menu name="Get Involved">
<item name="Overview"
@@ -59,6 +25,17 @@
href="http://jakarta.apache.org/getinvolved/mail.html"/>
<item name="Search Mailing lists"
href="http://marc.theaimsgroup.com/?l=alexandria-dev&r=1&w=2"/>
+ </menu>
+
+ <menu name="Cross reference">
+ <item name="by dependency"
+ href="http://jakarta.apache.org/builds/gump/latest/xref.html"/>
+ <item name="modules by repository"
+ href="http://jakarta.apache.org/builds/gump/latest/modxref.html"/>
+ <item name="installed packages"
+ href="http://jakarta.apache.org/builds/gump/latest/packages.html"/>
+ <item name="jars by module"
+ href="http://jakarta.apache.org/builds/gump/latest/cvsjars.html"/>
</menu>
</body>
1.60 +15 -4 jakarta-alexandria/proposal/gump/stylesheet/bash.xsl
Index: bash.xsl
===================================================================
RCS file: /home/cvs/jakarta-alexandria/proposal/gump/stylesheet/bash.xsl,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -r1.59 -r1.60
--- bash.xsl 2001/10/19 21:36:40 1.59
+++ bash.xsl 2001/10/20 20:50:33 1.60
@@ -113,7 +113,7 @@
<xsl:call-template name="select">
<xsl:with-param name="usage">
- Usage: update all \| project...
+ Usage: update all \| module...
</xsl:with-param>
</xsl:call-template>
@@ -342,13 +342,12 @@
<!-- =================================================================== -->
<xsl:template match="classpath">
- <xsl:text>export CLASSPATH=. </xsl:text>
+ <xsl:text>export CLASSPATH=$CP:$JAVA_HOME\lib\tools.jar </xsl:text>
<xsl:for-each select="pathelement">
<xsl:text>export CLASSPATH=$CLASSPATH:</xsl:text>
<xsl:value-of select="translate(@location,'\','/')"/>
<xsl:text> </xsl:text>
</xsl:for-each>
- <xsl:text>export CLASSPATH=$CLASSPATH:$CP </xsl:text>
</xsl:template>
<!-- =================================================================== -->
@@ -370,7 +369,19 @@
<xsl:value-of select="$cmd-prefix"/>
<xsl:text>" </xsl:text>
</xsl:if>
- <xsl:text>"java org.apache.tools.ant.Main</xsl:text>
+ <xsl:text>"java</xsl:text>
+
+ <xsl:if test="bootclass">
+ <xsl:text> -Xbootclasspath/p:</xsl:text>
+ <xsl:for-each select="bootclass">
+ <xsl:if test="position()!=1">
+ <xsl:text>:</xsl:text>
+ </xsl:if>
+ <xsl:value-of select="translate(@location,'\','/')"/>
+ </xsl:for-each>
+ </xsl:if>
+
+ <xsl:text> org.apache.tools.ant.Main</xsl:text>
<xsl:if test="@buildfile">
<xsl:text> -buildfile </xsl:text>
1.42 +5 -2 jakarta-alexandria/proposal/gump/stylesheet/build.xsl
Index: build.xsl
===================================================================
RCS file: /home/cvs/jakarta-alexandria/proposal/gump/stylesheet/build.xsl,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- build.xsl 2001/10/20 12:50:01 1.41
+++ build.xsl 2001/10/20 20:50:33 1.42
@@ -211,7 +211,7 @@
</xsl:for-each>
<xsl:for-each select="depend[not(noclasspath)]|option">
- <xsl:for-each select="jar">
+ <xsl:for-each select="jar[not(@type='boot')]">
<pathelement location="{../@home}/{@name}"/>
</xsl:for-each>
</xsl:for-each>
@@ -263,8 +263,11 @@
<xsl:apply-templates select="@*[name()!='target']"/>
<xsl:apply-templates select="/workspace/property"/>
- <xsl:apply-templates select="*"/>
+ <xsl:apply-templates select="*[name()!='bootclass']"/>
+ <xsl:for-each select="../depend/jar[@type='boot']">
+ <bootclass location="{../@home}/{@name}"/>
+ </xsl:for-each>
</xsl:copy>
</xsl:template>
1.16 +1 -1 jakarta-alexandria/proposal/gump/stylesheet/update.xsl
Index: update.xsl
===================================================================
RCS file: /home/cvs/jakarta-alexandria/proposal/gump/stylesheet/update.xsl,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- update.xsl 2001/10/20 12:50:01 1.15
+++ update.xsl 2001/10/20 20:50:33 1.16
@@ -13,7 +13,7 @@
</xsl:template>
<!-- =================================================================== -->
- <!-- provide support for specifying desired projects on the command line -->
+ <!-- provide support for specifying desired modules on the command line -->
<!-- =================================================================== -->
<xsl:template match="workspace">
1.29 +16 -5 jakarta-alexandria/proposal/gump/stylesheet/win2k.xsl
Index: win2k.xsl
===================================================================
RCS file: /home/cvs/jakarta-alexandria/proposal/gump/stylesheet/win2k.xsl,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- win2k.xsl 2001/10/20 14:57:48 1.28
+++ win2k.xsl 2001/10/20 20:50:33 1.29
@@ -77,8 +77,8 @@
<xsl:text> </xsl:text>
</xsl:for-each>
- <xsl:text>if not "%1"=="" echo Unknown project: %1 </xsl:text>
- <xsl:text>echo Usage: update all ^| project... </xsl:text>
+ <xsl:text>if not "%1"=="" echo Unknown module: %1 </xsl:text>
+ <xsl:text>echo Usage: update all ^| module... </xsl:text>
<xsl:text>goto eoj </xsl:text>
<xsl:text> :header </xsl:text>
@@ -303,13 +303,12 @@
<!-- =================================================================== -->
<xsl:template match="classpath">
- <xsl:text>SET CLASSPATH=. </xsl:text>
+ <xsl:text>SET CLASSPATH=%CP%;%JAVA_HOME%\lib\tools.jar </xsl:text>
<xsl:for-each select="pathelement">
<xsl:text>SET CLASSPATH=%CLASSPATH%;</xsl:text>
<xsl:value-of select="translate(@location,'/','\')"/>
<xsl:text> </xsl:text>
</xsl:for-each>
- <xsl:text>SET CLASSPATH=%CLASSPATH%;%CP% </xsl:text>
</xsl:template>
<!-- =================================================================== -->
@@ -319,7 +318,19 @@
<xsl:template match="ant">
<xsl:text>SET STATUS=SUCCESS </xsl:text>
- <xsl:text>java org.apache.tools.ant.Main</xsl:text>
+ <xsl:text>java</xsl:text>
+
+ <xsl:if test="bootclass">
+ <xsl:text> -Xbootclasspath/p:</xsl:text>
+ <xsl:for-each select="bootclass">
+ <xsl:if test="position()!=1">
+ <xsl:text>;</xsl:text>
+ </xsl:if>
+ <xsl:value-of select="translate(@location,'\','/')"/>
+ </xsl:for-each>
+ </xsl:if>
+
+ <xsl:text> org.apache.tools.ant.Main</xsl:text>
<xsl:if test="@buildfile">
<xsl:text> -buildfile </xsl:text>
---------------------------------------------------------------------
To unsubscribe, e-mail: alexandria-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: alexandria-dev-help@jakarta.apache.org