bodewig 01/03/09 04:04:05
Modified: docs/manual/Integration VAJAntTool.html
Log:
Documented default excluded of <vajexport>. Removed stray CRs.
Submitted by: David Rees <[EMAIL PROTECTED]>
Revision Changes Path
1.6 +62 -23 jakarta-ant/docs/manual/Integration/VAJAntTool.html
Index: VAJAntTool.html
===================================================================
RCS file: /home/cvs/jakarta-ant/docs/manual/Integration/VAJAntTool.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- VAJAntTool.html 2001/03/05 13:07:14 1.5
+++ VAJAntTool.html 2001/03/09 12:04:03 1.6
@@ -53,7 +53,8 @@
tool provides decent deployment support VAJ has not (out of the box).<br>
<h2><a name="tasks"></a>The Tasks</h2>
-At the moment there are three tasks which help integrating the VAJ repository
contents into an external build process:
+At the moment there are three tasks which help integrating the VAJ repository
+contents into an external build process:
<table cellpadding="2" cellspacing="2" border="0" width="500">
<tbody>
@@ -98,7 +99,8 @@
</tr>
<tr>
<td valign="Top">name</td>
- <td valign="Top">name of the VAJ project to load into the
workspace</td>
<td valign="Top" align="Center">yes</td>
+ <td valign="Top">name of the VAJ project to load into the
workspace</td>
+ <td valign="Top" align="Center">yes</td>
</tr>
<tr>
<td valign="Top">version</td>
@@ -122,7 +124,8 @@
<h3>Description:</h3>
<p>Exports Java source files, class files and/or resources from the workspace
-to the file system. Exports can be specified by giving the VAJ project
name and package name(s). This works very similar to <a
href="index.html#fileset">
+to the file system. Exports can be specified by giving the VAJ project
+name and package name(s). This works very similar to <a
href="index.html#fileset">
FileSets</a>. </p>
<h3>Parameters</h3>
@@ -161,7 +164,8 @@
</tr>
<tr valign="Top">
<td valign="Top">defaultexcludes </td>
- <td valign="Top">use default excludes when exporting (default: "yes")
<td valign="Top" align="Center">no</td>
+ <td valign="Top">use default excludes when exporting (default: "yes")
+ <td valign="Top" align="Center">no</td>
</tr>
</tbody>
</table>
@@ -214,13 +218,22 @@
</vajexport>
</pre>
This example exports all packages in the VAJ project 'MyProject', except
-packages starting with 'test'.
+packages starting with 'test'.
+<h3>Default Excludes</h3>
+The default excludes are:<br>
+<pre>
+ IBM*/**
+ Java class libraries/**
+ Sun class libraries*/**
+ JSP Page Compile Generated Code/**
+ VisualAge*/**
+</pre>
<hr>
<h2><a name="vajimport"></a>VAJImport</h2>
<h3>Description:</h3>
<p>Imports Java source files, class files and/or resources from the file
-system into VAJ. These imports can be specified with a fileset. </p>
+system into VAJ. These imports can be specified with a fileset. </p>
<h3>Parameters</h3>
<table border="1" cellpadding="2" cellspacing="0">
<tbody>
@@ -256,7 +269,8 @@
<h4>fileset</h4>
A <a href="index.html#fileset">FileSet</a> specifies the files to import.
-
<h3>Example</h3>
+
+<h3>Example</h3>
<pre>
<vajimport project="Test" importClasses="true">
<fileset dir="${import.dir}">
@@ -432,7 +446,8 @@
described below doesn't work for You, it's probably not Your fault
but incomplete/wrong instructions. In this case, please contact one
of the <a href="#authors">authors</a>.
-We assume <font face="Courier">C:\IBMVJava</font> as VAJ install
directory. If You have installed it elsewhere, adapt the pathes below.
+We assume <font face="Courier">C:\IBMVJava</font> as VAJ install
+directory. If You have installed it elsewhere, adapt the pathes below.
Execute following steps to get the PlugIn up and running:
<ul>
<li>install the Visual Age IDE Tools (via File->Quick Start->
@@ -449,60 +464,81 @@
<li>Create the directory <font face="Courier">
C:\IBMVJava\ide\tools\org-apache-tools-ant</font>.
</li>
- <li>export the Ant and XML parser class files into this directory. Be sure
to select class files and resources. Sources don't have to be exported.
Some optional tasks have errors and can't be exported when You
don't have the necessary packages in Your workspace (e.g. junit
task, ejbc task). If You need this tasks either import these packages
into VAJ, too, or copy the .class files directly from the binary
distribution.
+ <li>export the Ant and XML parser class files into this directory. Be sure
+ to select class files and resources. Sources don't have to be exported.
+ Some optional tasks have errors and can't be exported when You
+ don't have the necessary packages in Your workspace (e.g. junit
+ task, ejbc task). If You need this tasks either import these packages
+ into VAJ, too, or copy the .class files directly from the binary
+ distribution.
</li>
<li>copy <font face="Courier">default.ini</font> (in <font face="Courier">
jakarta-ant\src\...\taskdefs\optional\ide</font>) to <font
face="Courier">
C:\IBMVJava\ide\tools\org-apache-tools-ant\default.ini</font>.
</li>
- <li>if you want to access this help from the Workbench, create the
directory <font face="Courier">
C:\IBMVJava\ide\tools\org-apache-tools-ant\doc</font>
+ <li>if you want to access this help from the Workbench, create the
+ directory <font face="Courier">
C:\IBMVJava\ide\tools\org-apache-tools-ant\doc</font>
and copy the files <font face="Courier">VAJAntTool.html</font>,
<font face="Courier">toolmenu.gif</font> and <font face="Courier">
anttool1.gif</font> to it.
</li>
<li>VAJ has to be restarted to recognize the new tool.</li>
- <li>Now if You open the context menu of a project, You should see the entry
'Ant Build' in the Tools submenu (see <a href="#usage">Usage</a>).
+ <li>Now if You open the context menu of a project, You should see the entry
+ 'Ant Build' in the Tools submenu (see <a href="#usage">Usage</a>).
</li>
- <li>Make sure the tool works as expected. Now You can remove Ant and the
imported XML parser from Your workspace (and optionally add the
+ <li>Make sure the tool works as expected. Now You can remove Ant and the
+ imported XML parser from Your workspace (and optionally add the
IBM parser again).
</li>
</ul>
<hr>
<h2><a name="usage"></a>Usage</h2>
-Beeing sure the tool is installed correctly and your Ant build
file is configured, it is really easy to use.<br>
+Beeing sure the tool is installed correctly and your Ant build
+file is configured, it is really easy to use.<br>
Go to your Workbench, select the project you want to deploy and
open its context menu. In the submenu <i>Tools</i> you should find
-the new entry <i>Ant Build</i>. Klick it to start the tool!
<center><img src="toolmenu.gif" border="0" height="246" width="393"></center>
- After a short time this frame should pop up:
+the new entry <i>Ant Build</i>. Klick it to start the tool!
+
+<center><img src="toolmenu.gif" border="0" height="246" width="393"></center>
+ After a short time this frame should pop up:
<center><img src="anttool1.gif" border="0" height="222" width="389"></center>
- This frame contains the following elements:
+ This frame contains the following elements:
<ul>
<li>A menubar with some options described later</li>
<li>The name of your selected VAJ project</li>
- <li>An entry field for the Ant XML buildfile with a browse [...] button.
The full qualified filename, including the directory is needed here.
+ <li>An entry field for the Ant XML buildfile with a browse [...] button.
+ The full qualified filename, including the directory is needed here.
</li>
- <li>A list with tasks specified in the buildfile. Until your first save
of the build info (described later), this list will be empty. When
+ <li>A list with tasks specified in the buildfile. Until your first save
+ of the build info (described later), this list will be empty. When
loading a build file by the <i>Reload Project</i> button, this list
is filled with all tasks which have a description attribute. The
task you select in this list will be executed when pressing the
<i> Execute Task</i> button.
</li>
<li>A pulldown box for specifying the log level.</li>
- <li>Three buttons. Two of them I have already described and the third one
is just the <i>Close </i>button to exit our small tool!
+ <li>Three buttons. Two of them I have already described and the third one
+ is just the <i>Close </i>button to exit our small tool!
</li>
</ul>
-After you have set up your buildprocess you might find it useful
to save the data you've just entered, so we implemented an option to
save it to the repository into your selected project. Make sure that you
have an open edition of your project before selecting
+After you have set up your buildprocess you might find it useful
+to save the data you've just entered, so we implemented an option to
+save it to the repository into your selected project. Make sure that you
+have an open edition of your project before selecting
<i>Save BuildInfo To Repository</i> from the <i>File</i> menu.
Now your information is saved to this edition of your project and will
be loaded automatically the next time you start <i>Ant Build</i>.<br>
-If you have closed the log window accidentally, it can be reopened
with the <i>Log</i> item in the <i>File</i> menu, and if you want to
know who developed this, just select <i>About</i> in the <i>Help</i> menu.
+If you have closed the log window accidentally, it can be reopened
+with the <i>Log</i> item in the <i>File</i> menu, and if you want to
+know who developed this, just select <i>About</i> in the <i>Help</i> menu.
<hr>
<h2><a name="faq"></a>Frequently Asked Questions</h2>
<p><b>Q: I want to load, export and build more then one Visual Age project
to one jar! How to?</b><br>
-A: The VA tasks are able to load and export several Projects all
at once. You can choose whatever project you like for storing the tool
+A: The VA tasks are able to load and export several Projects all
+at once. You can choose whatever project you like for storing the tool
information, it doesn't really matter
</p>
<p><b>Q: When I load my build file, the list of targets is empty.
Why?</b><br>
@@ -563,7 +599,10 @@
<hr>
<h2><a name="va_versions"></a>VisualAge for Java Versions</h2>
-This tool integration has been tested with versions 3.02 and 3.5
of VisualAge for Java. It should run with the 2.x Versions, too, but
we didn't try. The graphical user interface is build with AWT so it is
JDK independent by now.
+This tool integration has been tested with versions 3.02 and 3.5
+of VisualAge for Java. It should run with the 2.x Versions, too, but
+we didn't try. The graphical user interface is build with AWT so it is
+JDK independent by now.
<hr>
<h2><a name="history"></a>History</h2>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
