You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by je...@apache.org on 2002/04/05 05:08:31 UTC

cvs commit: jakarta-avalon-excalibur README.txt depchecking.sh

jefft       02/04/04 19:08:31

  Modified:    .        Tag: depchecking README.txt No tag depchecking.sh
  Log:
  Update the README, and remove phrases that will seem obsolete in a few months
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.4.2.2   +21 -20    jakarta-avalon-excalibur/README.txt
  
  Index: README.txt
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-excalibur/README.txt,v
  retrieving revision 1.4.2.1
  retrieving revision 1.4.2.2
  diff -u -r1.4.2.1 -r1.4.2.2
  --- README.txt	1 Apr 2002 05:46:10 -0000	1.4.2.1
  +++ README.txt	5 Apr 2002 03:08:31 -0000	1.4.2.2
  @@ -5,7 +5,8 @@
     -----------
   
     Excalibur is a collection of often-needed reusable components. It includes tools for
  -  threading, pooling, datasources, CLI option parsing and more.
  +  threading, pooling, datasources, command-line interface (CLI) option parsing
  +  and more.
   
     Where is it?
     ------------
  @@ -15,14 +16,19 @@
     Directory Layout
     ----------------
   
  -  Recently, Excalibur was broken up from a single monolithic jar, to a number
  -  of reusable components. These components are what you see in all the
  -  subdirectories.
  +  Excalibur is comprised of a number reusable components. These components are
  +  what you see in most of the subdirectories.
  +
  +  The all/ directory contains a core set of packages that cannot be
  +  componentized further (excalibur-core.jar). It is a legacy of a time before
  +  Excalibur was componentized, and as such, it's build system has much
  +  functionality not yet present elsewhere. In time, functionality in
  +  all/build.xml will migrate to ./build.xml.
   
     The avalon-excalibur.jar released in version 4.1 would now consist of the
     following jars:
   
  -   all/build/lib/excalibur-core.jar
  +   all/build/lib/avalon-excalibur.jar
      cli/build/lib/excalibur-cli-1.0.jar
      collections/build/lib/excalibur-collections-1.0.jar
      concurrent/build/lib/excalibur-concurrent-1.0.jar
  @@ -34,6 +40,9 @@
   
      instrument/build/lib/excalibur-instrument-0.1.jar
   
  +   Typing 'ant' in the root directory will build an avalon-excalibur.jar
  +   containing these components.
  +
   
     Component dependencies
     ----------------------
  @@ -44,23 +53,15 @@
     your local environment. See the text in ant.properties.sample for more
     information.
   
  -  [Update 2001-03-29]
  -
  -    To date, there remains a core set of packages which are too interrelated to
  -    break up further. These reside in the all/ directory. This core set should
  -    be regarded as a component in it's own right. Like any other component, it
  -    has dependencies on other Excalibur components, recorded in
  -    ant.properties.sample.
  -
  -    The documentation system for all components is still completely within the
  -    all/ directory. Type 'ant html-docs' in all/ to build the HTML
  -    documentation. This will be fixed in the near future.
  +  In general, it is safe to type 'ant', and if an external dependency is
  +  missing, you will be prompted on what to add to ant.properties
   
   
     General Building Requirements
     -----------------------------
   
     -JDK1.2 or above
  +  -Jakarta Ant 1.4.1 or higher, with optional.jar and junit.jar in $ANT_HOME/lib
     -To build from CVS you must set JAVA_HOME to the jdk dir (eg:/usr/bin/jdk1.2 or
      c:\jdk1.3)
     -To build Informix drivers you need version 2.2 of the JDBC driver
  @@ -71,10 +72,10 @@
     ---------------
   
     Generally, one would build individual components, not the whole of Excalibur.
  -  However, as noted above, there is a core set of packages, living in all/,
  -  that generally constitute what people call 'Excalibur'. To build this, you'll
  -  first need to build it's dependencies (listed in all/ant.properties.sample).
  -  Then running Ant in all/ should generate the core jar in build/lib/
  +  This can be done by typing 'ant' in any component's directory.
  +  However, if you type 'ant' in the project root, a file 'avalon-excalibur.jar'
  +  will be built, containing a set of components historically regarded as
  +  comprising 'Excalibur'.
   
   
     Problems?
  
  
  
  No                   revision
  
  
  No                   revision
  
  
  1.7       +1 -1      jakarta-avalon-excalibur/depchecking.sh
  
  Index: depchecking.sh
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-excalibur/depchecking.sh,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- depchecking.sh	4 Apr 2002 22:49:58 -0000	1.6
  +++ depchecking.sh	5 Apr 2002 03:08:31 -0000	1.7
  @@ -2,4 +2,4 @@
   # any other files.  To go back to the CVS HEAD version of these files, use 'cvs
   # update -A' with the same file list.
   
  -cvs update -r depchecking depchecker.xml dependencies.txt collections/build.xml build.xml all/build.xml util/build.xml instrument/build.xml command/build.xml baxter/build.xml bzip2/build.xml cache/build.xml cli/build.xml event/build.xml extension/build.xml i18n/build.xml io/build.xml naming/build.xml tar/build.xml template-product/build.xml zip/build.xml instrument-client/build.xml instrument-manager/build.xml concurrent/build.xml collections/default.properties all/default.properties util/default.properties instrument/default.properties command/default.properties baxter/default.properties bzip2/default.properties cache/default.properties cli/default.properties event/default.properties extension/default.properties i18n/default.properties io/default.properties naming/default.properties tar/default.properties template-product/default.properties zip/default.properties instrument-client/default.properties instrument-manager/default.properties default.properties concurrent/default.properties collections/project.properties instrument/project.properties command/project.properties baxter/project.properties bzip2/project.properties cache/project.properties cli/project.properties event/project.properties extension/project.properties i18n/project.properties io/project.properties naming/project.properties tar/project.properties template-product/project.properties zip/project.properties instrument-client/project.properties instrument-manager/project.properties concurrent/project.properties collections/ant.properties.sample all/ant.properties.sample util/ant.properties.sample ant.properties.sample instrument/ant.properties.sample command/ant.properties.sample baxter/ant.properties.sample bzip2/ant.properties.sample cache/ant.properties.sample cli/ant.properties.sample event/ant.properties.sample extension/ant.properties.sample i18n/ant.properties.sample io/ant.properties.sample naming/ant.properties.sample tar/ant.properties.sample template-product/ant.properties.sample zip/ant.properties.sample instrument-client/ant.properties.sample instrument-manager/ant.properties.sample concurrent/ant.properties.sample altrmi/build.xml altrmi/default.properties command/build.xml command/default.properties lang/build.xml lang/default.properties logger/build.xml logger/default.properties testcase/build.xml testcase/default.properties thread/build.xml thread/default.properties fortress/build.xml fortress/default.properties 
  +cvs update -r README.txt depchecking depchecker.xml dependencies.txt collections/build.xml build.xml all/build.xml util/build.xml instrument/build.xml command/build.xml baxter/build.xml bzip2/build.xml cache/build.xml cli/build.xml event/build.xml extension/build.xml i18n/build.xml io/build.xml naming/build.xml tar/build.xml template-product/build.xml zip/build.xml instrument-client/build.xml instrument-manager/build.xml concurrent/build.xml collections/default.properties all/default.properties util/default.properties instrument/default.properties command/default.properties baxter/default.properties bzip2/default.properties cache/default.properties cli/default.properties event/default.properties extension/default.properties i18n/default.properties io/default.properties naming/default.properties tar/default.properties template-product/default.properties zip/default.properties instrument-client/default.properties instrument-manager/default.properties default.properties concurrent/default.properties collections/project.properties instrument/project.properties command/project.properties baxter/project.properties bzip2/project.properties cache/project.properties cli/project.properties event/project.properties extension/project.properties i18n/project.properties io/project.properties naming/project.properties tar/project.properties template-product/project.properties zip/project.properties instrument-client/project.properties instrument-manager/project.properties concurrent/project.properties collections/ant.properties.sample all/ant.properties.sample util/ant.properties.sample ant.properties.sample instrument/ant.properties.sample command/ant.properties.sample baxter/ant.properties.sample bzip2/ant.properties.sample cache/ant.properties.sample cli/ant.properties.sample event/ant.properties.sample extension/ant.properties.sample i18n/ant.properties.sample io/ant.properties.sample naming/ant.properties.sample tar/ant.properties.sample template-product/ant.properties.sample zip/ant.properties.sample instrument-client/ant.properties.sample instrument-manager/ant.properties.sample concurrent/ant.properties.sample altrmi/build.xml altrmi/default.properties command/build.xml command/default.properties lang/build.xml lang/default.properties logger/build.xml logger/default.properties testcase/build.xml testcase/default.properties thread/build.xml thread/default.properties fortress/build.xml fortress/default.properties 
  
  
  

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>