                AddAllSubPackagesAddin for JBuilder Foundation
                   by David P. White (dpwhite@halcyon.com)
                           version 0.01 3/03/2000

Introduction
------------
This software in provided as is and carries no warrantee of any kind. Should
you encounter problems please feel free to let me know. Thanks.

This .jar file contains source and executable java code to provide basic but
needed file printing support for theJBuilder Foundation IDE environment. This
is performed using the Opentools API published with the initial release of
JBF. Should that API change in future releases, this code may not continue to
work as expected. However, because it only makes use of a small portion of the
Opentools API I would guess that it will remain usable for some time.

After setup and installation, you need to restart JBF. When you do, you should
now see the addin's banner displayed on the console. Once JBF has completed
loading, you will notice a new menu item on the project pane's context menu if
you have selected a single, package that has been previously added to your JBF
project.

Installation
------------
(1)  Place the .jar file into an acceptable location. I personally create an
extensions sub-directory under the Jbuilder root dir and I place the
.jar file there. JBF supports a directory called lib/ext into which you should
be able to simply place a .jar file which JBF will automatically load but this
is broken under Windows for some reason and only the first .jar file actually
gets loaded.

(2)  You need to update the classpath used by JBuilder Foundation to point to
the addin's .jar file. I recommend doing this by updating the JBF startup
script (which on my NT box is in the JBuilder\bin directory). Near the end of
this script, is a place to set an environment variable called tempcp. I place
my addin (and supporting) classpath stuff here. So on my system the line is:

set
tempcp=%JBUILDER_HOME%\extensions\AddAllSubPackagesAddin.jar

Of course, you can just add the .jar file to your normal classpath variable as
well.

(3)  Now you should start/re-start JBF.You should see the menu item on the
project pane's context menu if a single package node is selected.

Usage
-----
(1)  You should be able to select any added package node. The addin will
process only those subpackages of the selected node.

(2)  It is assumed that any sub-directory in the tree under the selected node
will be a subpackage. While this may not always be the case, it true of most
java projects.

(3)  Each sub-directory must contain at least one file. If there are no files
in the sub-directory, it will NOT be recognized as a sub-project. This should
present no real troubles as a sub-directory with no files will not constitute
much of a package.

(4)  The addin does not handle renaming or moving of subpackages. Occasionally
removing all but the most top level package in the tree and re-running the
addin should deal with moves and re-names.

(5)  You can re-run the addin on a package as many times as you like. In fact,
I run it daily to capture any packages that have been newly added by my team
members. Unlike JBF's default behavior when adding a package multiple times,
this addin will NOT add a subpackage that is already in the project.
