blob: d404d625ecb3795d81874ecc8776e0efa87a9ae2 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
<HEAD>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<title>Generating the build.xml file</title>
</HEAD>
<BODY BGCOLOR="#ffffff">
<h3>Generating the build.xml file</h3>
<P CLASS="Para">Open one of the navigation views and locate your new plug-in project.</P>
<ol>
<li>Select the file 'plugin.xml' underneath your new project and right-click
<b>PDE Tools &gt; Create Ant Build File</b>.</li>
<li>A new file, 'build.xml' will be created underneath your project.</li>
<li>Open the Ant editor on the build.xml file by double clicking it in one of
the navigation views. Notice that for this file, the Ant editor is the default
editor. This is because by default, there is a file association in the general
preferences associating files named 'build.xml' with the Ant editor. <br>
<img src="../images/Image607_buildxml.png" alt="default build.xml file" border="0" ></li>
</ol>
<p>The build.xml file is a default Ant buildfile with many targets useful for deploying
your plug-in. For example, there are individual targets to build all necessary
jars for your plug-in, create a .zip file containing everything in your plug-in,
cleanup any .zip files that may have been created and so on. </p>
<p>Now that we have the build.xml file, we will use it to build a .jar file for
our plug-in.</p>
</BODY>
</HTML>