bundles/org.eclipse.pde.doc.user/guide/pde_custom_callbacks.htm - platform/eclipse.platform.common - Git at Google

 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
 <html>
 <head>
   <meta name="copyright"
  content="Copyright (c) IBM Corporation and others 2006. 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>Customizing feature and plug-in builds</title>
 </head>
 <body style="background-color: rgb(255, 255, 255);">
 <h1>Feature and Plug-in custom build steps</h1>
 <p>New in 3.2 is the ability for a feature or plug-in to contribute
 custom custom steps to its own build.&nbsp; These custom steps can be
 used for things like instrumenting byte-code after compilation,
 indexing help files for documentation, or copying extra files into the
 bundle.&nbsp;</p>
 <p>To use custom targets, a feature or plug-in must define the property
 <tt>customBuildCallbacks</tt> in its build.properties file; the value
 of this
 property is the location of an xml file, relative to the root of the
 feature/plug-in, containing the custom targets.&nbsp; Templates named
 <span style="font-style: italic;">customBuildCallbacks.xml</span>
 containing the supported custom targets are
 provided in org.eclipse.pde.build/templates/plugins and&nbsp;
 org.eclipse.pde.build/templates/features respectively.&nbsp; These
 templates can be copied into your feature/plug-in and modified as
 needed.&nbsp; The custom targets will be invoked using the subant task
 with failonerror="false", so that the build will containue if your
 custom xml file does not contain a particular target or an error occurs
 .<br>
 </p>
 <h2>Plug-ins</h2>
 <p>The generated build.xml that builds a plug-in contains several
 targets that perform specific tasks.&nbsp; PDE Build allows the plug-in
 to provide custom pre and post targets that will be called before and
 after specific tasks.&nbsp; In addition to any ant properties that may
 already be defined, each custom target may also be passed a couple of
 specific properties.&nbsp; The following targets support custom
 callbacks:<br>
 </p>
 <ul>
   <li><span style="font-weight: bold;">build.jars</span>:&nbsp; The
 build.jars target will invoke in turn each of the compilation targets
 that will be built for this bundle.&nbsp; It supports <span
  style="font-weight: bold;">pre.build.jars</span> and <span
  style="font-weight: bold;">post.build.jars</span> targets which are
 called before and after all the compilation targets are called.&nbsp;
 Both the pre and post targets are provided with the property <tt>build.result.folder</tt>
 which is the folder to which the
 results of the
 build will be copied.<br>
     <span style="font-weight: bold;"></span></li>
   <li><span style="font-weight: bold;">Compilation Targets</span>:&nbsp;
 The build.xml defines a compilation target for each jar being built (eg
 @dot for the bundle itself, or library.jar).&nbsp; Each compilation
 target supports 3 custom callbacks:</li>
   <ul>
     <li><span style="font-weight: bold;">pre.&lt;compilation target&gt;</span>:&nbsp;
 Called before source files are compiled.&nbsp; It is provided with the
 following properties:</li>
     <ul>
       <li><tt>target.folder</tt>:&nbsp; The folder where the compiled
 class
 files will be placed</li>
       <li><tt>source.folder&lt;N&gt;</tt>:&nbsp; The source folder(s)
 containing
 the source to be compiled.&nbsp; (eg <tt>source.folder1</tt>, <tt>source.folder2</tt>,
 etc).</li>
       <li><tt>&lt;compilation target&gt;.classpath</tt>:&nbsp; A
 reference to
 the ant path structure containing the classpath that will be used in
 the compilation.&nbsp; (eg <tt>@dot.classpath</tt>, <tt>library.jar.classpath</tt>)</li>
     </ul>
     <li><span style="font-weight: bold;">post.compile.&lt;compilation
 target&gt;</span>:&nbsp; Called after the source is compiled, but
 before the class files are jared or copied into the build result
 folder.&nbsp;
 It is provided with the same properties as the pre.&lt;compilation
 target&gt; target.</li>
     <li><span style="font-weight: bold;">post.&lt;compilation target&gt;</span>:&nbsp;
 Called at the end of the compilation target after the results are
 copied to the build result folder.&nbsp; It is provided with the
 following properties:</li>
     <ul>
       <li>jar.Location:&nbsp; The jar or folder containing the
 compilation results.</li>
       <li>&lt;compilation target&gt;.classpath:&nbsp; A reference to
 the ant path structure containing the classpath that was used in the
 compilation.</li>
     </ul>
   </ul>
   <li><span style="font-weight: bold;">build.sources</span>:&nbsp; This
 target builds the source zips for each of the compilation
 targets.&nbsp; It supports <span style="font-weight: bold;">pre.build.sources</span>
 and <span style="font-weight: bold;">post.build.sources</span>
 targets.&nbsp; Both of these targets are provided with the property
 build.result.folder which is the folder to which the source zip files
 will be copied.</li>
   <li><span style="font-weight: bold;">gather.bin.parts</span>:&nbsp;
 This target copies the build results (ie the jars and any other files
 being included in the bundle) to the final destination directory.&nbsp;
 It is also the target where the version qualifiers are replaced in the
 manifest file (see&nbsp;<a href="pde_version_qualifiers.htm">Version
 Qualifiers</a>). It supports <span style="font-weight: bold;">pre.gather.bin.parts</span>
 and <span style="font-weight: bold;">post.gather.bin.parts</span>
 targets.&nbsp; Two properties are provided to the pre and post targets:</li>
   <ul>
     <li><tt>build.result.folder</tt>:&nbsp; the folder containing the
 results of
 the build</li>
     <li><tt>target.folder</tt>:&nbsp; the destination folder to which
 the build
 results and bundle contents are being copied.</li>
   </ul>
   <li><span style="font-weight: bold;">gather.sources</span>: This
 target gathers the source zips for the bundle.&nbsp; It supports <span
  style="font-weight: bold;">pre.gather.sources </span>and <span
  style="font-weight: bold;">post.gather.sources</span> targets.&nbsp;
 Both the pre
 and post targets are provided with the target.folder property which is
 the folder that the sources are being copied to.<br>
   </li>
   <li><span style="font-weight: bold;">gather.logs</span>:&nbsp; This
 target collects the log files from the build.&nbsp; It supports <span
  style="font-weight: bold;">pre.gather.logs</span> and <span
  style="font-weight: bold;">post.gather.logs</span>.&nbsp; Both the pre
 and post
 targets are provided with the destination.temp.folder which is the
 temporary folder that the logs files are being copied to.<br>
   </li>
   <li><span style="font-weight: bold;">clean</span>:&nbsp; This target
 performs a clean, it supports <span style="font-weight: bold;">pre.clean</span>
 and <span style="font-weight: bold;">post.clean</span> targets.&nbsp;
 The pre and post targets have the following properties:</li>
   <ul>
     <li><tt>plugin.destination</tt>:&nbsp; The folder that the final
 bundle was
 copied to.<br>
     </li>
     <li><tt>build.result.folder</tt>:&nbsp; The folder that the results
 of the
 build were copied to</li>
     <li><tt>temp.folder</tt>:&nbsp; The temporary folder where where
 results
 were staged before being copied to the final desination.<br>
     </li>
   </ul>
 </ul>
 <h2>Features</h2>
 <p>
 The generated build.xml for features only supports custom build
 callbacks for the gather.bin.parts target.&nbsp; This target will
 invoke that gather.bin.parts target of all the included features and
 plug-ins.&nbsp; It supports pre.gather.bin.parts and
 post.gather.bin.parts.&nbsp; Both of these targets are provided with
 the following properties:
 </p>
 <ul>
   <li><tt>destination.temp.folder</tt>:&nbsp; The directory to which
 the plugins
 will be copied.</li>
   <li><tt>feature.directory</tt>:&nbsp; The directory to which the
 files for
 this feature will be copied.<br>
   </li>
 </ul>
 </body>
 </html>
	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
	<html>
	<head>
	<meta name="copyright"
	content="Copyright (c) IBM Corporation and others 2006. 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>Customizing feature and plug-in builds</title>
	</head>
	<body style="background-color: rgb(255, 255, 255);">
	<h1>Feature and Plug-in custom build steps</h1>
	<p>New in 3.2 is the ability for a feature or plug-in to contribute
	custom custom steps to its own build.  These custom steps can be
	used for things like instrumenting byte-code after compilation,
	indexing help files for documentation, or copying extra files into the
	bundle. </p>
	<p>To use custom targets, a feature or plug-in must define the property
	<tt>customBuildCallbacks</tt> in its build.properties file; the value
	of this
	property is the location of an xml file, relative to the root of the
	feature/plug-in, containing the custom targets.  Templates named
	<span style="font-style: italic;">customBuildCallbacks.xml</span>
	containing the supported custom targets are
	provided in org.eclipse.pde.build/templates/plugins and
	org.eclipse.pde.build/templates/features respectively.  These
	templates can be copied into your feature/plug-in and modified as
	needed.  The custom targets will be invoked using the subant task
	with failonerror="false", so that the build will containue if your
	custom xml file does not contain a particular target or an error occurs
	.<br>
	</p>
	<h2>Plug-ins</h2>
	<p>The generated build.xml that builds a plug-in contains several
	targets that perform specific tasks.  PDE Build allows the plug-in
	to provide custom pre and post targets that will be called before and
	after specific tasks.  In addition to any ant properties that may
	already be defined, each custom target may also be passed a couple of
	specific properties.  The following targets support custom
	callbacks:<br>
	</p>
	<ul>
	<li><span style="font-weight: bold;">build.jars</span>:  The
	build.jars target will invoke in turn each of the compilation targets
	that will be built for this bundle.  It supports <span
	style="font-weight: bold;">pre.build.jars</span> and <span
	style="font-weight: bold;">post.build.jars</span> targets which are
	called before and after all the compilation targets are called.
	Both the pre and post targets are provided with the property <tt>build.result.folder</tt>
	which is the folder to which the
	results of the
	build will be copied.<br>
	<span style="font-weight: bold;"></span></li>
	<li><span style="font-weight: bold;">Compilation Targets</span>:
	The build.xml defines a compilation target for each jar being built (eg
	@dot for the bundle itself, or library.jar).  Each compilation
	target supports 3 custom callbacks:</li>
	<ul>
	<li><span style="font-weight: bold;">pre.<compilation target></span>:
	Called before source files are compiled.  It is provided with the
	following properties:</li>
	<ul>
	<li><tt>target.folder</tt>:  The folder where the compiled
	class
	files will be placed</li>
	<li><tt>source.folder<N></tt>:  The source folder(s)
	containing
	the source to be compiled.  (eg <tt>source.folder1</tt>, <tt>source.folder2</tt>,
	etc).</li>
	<li><tt><compilation target>.classpath</tt>:  A
	reference to
	the ant path structure containing the classpath that will be used in
	the compilation.  (eg <tt>@dot.classpath</tt>, <tt>library.jar.classpath</tt>)</li>
	</ul>
	<li><span style="font-weight: bold;">post.compile.<compilation
	target></span>:  Called after the source is compiled, but
	before the class files are jared or copied into the build result
	folder.
	It is provided with the same properties as the pre.<compilation
	target> target.</li>
	<li><span style="font-weight: bold;">post.<compilation target></span>:
	Called at the end of the compilation target after the results are
	copied to the build result folder.  It is provided with the
	following properties:</li>
	<ul>
	<li>jar.Location:  The jar or folder containing the
	compilation results.</li>
	<li><compilation target>.classpath:  A reference to
	the ant path structure containing the classpath that was used in the
	compilation.</li>
	</ul>
	</ul>
	<li><span style="font-weight: bold;">build.sources</span>:  This
	target builds the source zips for each of the compilation
	targets.  It supports <span style="font-weight: bold;">pre.build.sources</span>
	and <span style="font-weight: bold;">post.build.sources</span>
	targets.  Both of these targets are provided with the property
	build.result.folder which is the folder to which the source zip files
	will be copied.</li>
	<li><span style="font-weight: bold;">gather.bin.parts</span>:
	This target copies the build results (ie the jars and any other files
	being included in the bundle) to the final destination directory.
	It is also the target where the version qualifiers are replaced in the
	manifest file (see <a href="pde_version_qualifiers.htm">Version
	Qualifiers</a>). It supports <span style="font-weight: bold;">pre.gather.bin.parts</span>
	and <span style="font-weight: bold;">post.gather.bin.parts</span>
	targets.  Two properties are provided to the pre and post targets:</li>
	<ul>
	<li><tt>build.result.folder</tt>:  the folder containing the
	results of
	the build</li>
	<li><tt>target.folder</tt>:  the destination folder to which
	the build
	results and bundle contents are being copied.</li>
	</ul>
	<li><span style="font-weight: bold;">gather.sources</span>: This
	target gathers the source zips for the bundle.  It supports <span
	style="font-weight: bold;">pre.gather.sources </span>and <span
	style="font-weight: bold;">post.gather.sources</span> targets.
	Both the pre
	and post targets are provided with the target.folder property which is
	the folder that the sources are being copied to.<br>
	</li>
	<li><span style="font-weight: bold;">gather.logs</span>:  This
	target collects the log files from the build.  It supports <span
	style="font-weight: bold;">pre.gather.logs</span> and <span
	style="font-weight: bold;">post.gather.logs</span>.  Both the pre
	and post
	targets are provided with the destination.temp.folder which is the
	temporary folder that the logs files are being copied to.<br>
	</li>
	<li><span style="font-weight: bold;">clean</span>:  This target
	performs a clean, it supports <span style="font-weight: bold;">pre.clean</span>
	and <span style="font-weight: bold;">post.clean</span> targets.
	The pre and post targets have the following properties:</li>
	<ul>
	<li><tt>plugin.destination</tt>:  The folder that the final
	bundle was
	copied to.<br>
	</li>
	<li><tt>build.result.folder</tt>:  The folder that the results
	of the
	build were copied to</li>
	<li><tt>temp.folder</tt>:  The temporary folder where where
	results
	were staged before being copied to the final desination.<br>
	</li>
	</ul>
	</ul>
	<h2>Features</h2>
	<p>
	The generated build.xml for features only supports custom build
	callbacks for the gather.bin.parts target.  This target will
	invoke that gather.bin.parts target of all the included features and
	plug-ins.  It supports pre.gather.bin.parts and
	post.gather.bin.parts.  Both of these targets are provided with
	the following properties:
	</p>
	<ul>
	<li><tt>destination.temp.folder</tt>:  The directory to which
	the plugins
	will be copied.</li>
	<li><tt>feature.directory</tt>:  The directory to which the
	files for
	this feature will be copied.<br>
	</li>
	</ul>
	</body>
	</html>