This extension point is used to provide a remote build style for iSeries projects. A build style will usually provide at least one push operation to move changed elements to the target system, as well as at least one build operation to build the appropriate build targets for the project. Other operations may be supplied as needed.
<!ELEMENT extension (buildStyle*)>
<!ATTLIST extension
point CDATA #REQUIRED
id CDATA #IMPLIED
name CDATA #IMPLIED
>
<!ELEMENT buildStyle EMPTY>
<!ATTLIST buildStyle
id CDATA #REQUIRED
name CDATA #REQUIRED
class CDATA #REQUIRED
>
The following portion of the extender's plugin.xml shows the contribution of two build styles.
<extension point="com.ibm.etools.iseries.remotebuild.buildStyle"> <buildStyle name="XYZ Build Style" class="com.xyz.tools.styles.XYZBuildStyle" id="com.xyz.tools.styles.XYZBuildStyle"> </buildStyle> <buildStyle name="ABC Build Style" class="com.xyz.tools.styles.ABCBuildStyle" id="com.xyz.tools.styles.ABCBuildStyle"> </buildStyle> </extension>
Implementers of a build style must provide an implementation
of
com.ibm.etools.iseries.remotebuild.IBuildStyle
.
This should not be directly implemented.
Implementers should subclass
com.ibm.etools.iseries.remotebuild.BuildStyle
.
There are two supplied implementations of this extension point.
The CL Program build style will compile the COMPILE
and
BIND
members of the source file
associated-library/build-source-file
using CRTBNDCL
and then run those programs.
The command build style will submit the command specified in its configuration.
Both of these build styles provide push operations that will upload either the selected, or all changed resources in a project, to their corresponding locations on a host system.
Both of these build styles also modify the library list prior to invoking their respective actions by pushing the associated library into the library list as the current library.
(C) Copyright IBM Corp. 2002 All Rights Reserved.