leosimons    2003/01/19 03:00:20

  Added:       .        minimal-workspace.xml
               profile  minimal-profile.xml
  Log:
  add a braindead-simple minimal project definition as a sample for easily getting 
gump running on ones own machine
  
  Revision  Changes    Path
  1.1                  jakarta-gump/minimal-workspace.xml
  
  Index: minimal-workspace.xml
  ===================================================================
  <?xml version="1.0" ?>
  
  <!--
        See http://jakarta.apache.org/gump/workspace.html for the
        informal dtd of this xml file and more details about the
        possible elements.
        
        This is just about the most barebones workspace definition
        possible. To get started, rename this file to be the same
        as your machine hostname (%COMPUTERNAME% under windows),
        then set the basedir, where gump should check out material
        and build stuff. If you use any packages available as
        binaries only, you need to set pkgdir as well.
  -->
  <workspace basedir="C:\jakarta" pkgdir="C:\opt" version="0.3">
  
        <!-- this tells Ant to completely ignore all classpath
             elements in build scripts. This makes sure we build
             the latest version of everything. Note you could
             comment out this line and gump would still run fine.
             The thing you loose then is the continuous integration.
             See: http://jakarta.apache.org/gump/why.html for more
             background. -->
        <property name="build.sysclasspath" value="only"/>
  
        <!-- this references your profile description. A profile is a
             collection of projects and repositories that are logically
             to be considered a unit. A profile can provide a consistent
             set of installable dependencies, or tagged versions of cvs
             modules to be used.-->
        <profile href="profile/minimal-profile.xml"/>
  
        <!-- Repository overrides can be used to override the cvs repository
             definitions in the repository/ dir. This is handy if you want to
             check out using a different method than the default one, for
             example using ssh tunneling or a local machine connection.
             
             As I am a committer to parts of jakarta, I use ssh tunnelling and
             a different cvsroot, so the cvs checkout gives me write access to
             the jakarta modules. -->
        <!--<repository name="jakarta" method="ext" user="leosimons" 
path="/home/cvs"/>-->
  </workspace>
  
  
  
  1.1                  jakarta-gump/profile/minimal-profile.xml
  
  Index: minimal-profile.xml
  ===================================================================
  <!--
        See http://jakarta.apache.org/gump/profile.html for the
        informal dtd of this xml file and more details about the
        possible elements.
        
        This is just about the most barebones profile definition
        possible; it only references the couple most commonly used
        libraries. To get started, copy additional entries from the
        gump.xml file, and when you add new project definitions for
        your own software, reference those from here as well.
  -->
  <profile name="minimal">
    <!-- References to modules definitions. While a complete module
         can be defined here, typically one is referenced via href.
         A module is a collection of projects stored in a single cvs
         repository. See http://jakarta.apache.org/gump/module.html
         for more information. --> 
  
    <module href="project/jakarta-ant.xml"/>
    <module href="project/jakarta-ant-antidote.xml"/>
    <module href="project/xml-commons.xml"/>
    <module href="project/xml-crimson.xml"/>
    <module href="project/xml-xalan.xml"/>
    <module href="project/xml-xerces.xml"/>
    <module href="project/xml-xerces2.xml"/>
    <module href="http://cvs.apache.org/viewcvs/~checkout~/xml-forrest/module.xml"/>
    <module href="project/xml-stylebook.xml"/>
    <module href="project/junit.xml"/>
  
    <!-- References to installed binary projects. This is used for
         projects installed as packages rather than being built by
         gump. Examples are binary packages distributed by sun. The
         package attribute references the directory where you
         installed the package relative to the workspace pkgdir
         definition.
         See http://jakarta.apache.org/gump/project.html for more
         information. --> 
    <!--<project name="aspectj"        package="aspectj1.0"/>-->
  
    <!-- References to cvs repository definitions. You should leave
         all of these in here and add any references to your own
         cvs repositories.
         See http://jakarta.apache.org/gump/repository.html for more
         information. --> 
    <repository href="repository/dbxml.xml"/>
    <repository href="repository/devworks.xml"/>
    <repository href="repository/exolab.xml"/>
    <repository href="repository/jakarta.xml"/>
    <repository href="repository/jdom.xml"/>
    <repository href="repository/mozilla.xml"/>
    <repository href="repository/tigris.xml"/>
    <repository href="repository/sourceforge.xml"/>
    <repository href="repository/webmacro.xml"/>
    <repository href="repository/werken.xml"/>
    <repository href="repository/whichever.xml"/>
    <repository href="repository/xml.xml"/>
  
    <!-- server definitions. I have no idea what these are for. Leaving
         them doesn't harm. -->
    <server href="server/daedalus.apache.org.xml"/>
    <server href="server/icarus.apache.org.xml"/>
  
  </profile>
  
  
  
  

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to