It is simle as the macrodef defines a task named ibmwmqcreateBar that can be used like any other task.
Here is an example call:
<property name="ibmmqsicommon.location" location="ibmmqsicommon.xml"/>
<import file="${ibmmqsicommon.location}"/>
<path id="files.path">
<fileset dir="${esbtempbuild.dir}/">
<include name="**/MasterFlow*.msgflow"/>
<include name="**/Niceflow.msgflow"/>
</fileset>
</path>
<property name="included_projects" value="Flows CommonJava JavaFlows CommonESQL"/>
<pathconvert property="string.files.path" refid="files.path" pathsep=" ">
<map from="${tempbuild.dir}/" to=""/>
</pathconvert>
<pathconvert property="string.classpath.path" refid="classpath.path" pathsep=";"/>
<ibmwmqcreateBar workspacedirectory="${esbtempbuild.dir}"
barfilename="${bar.file}"
projectnames="${included_projects}"
filepaths="${string.files.path}"
classpath="${string.classpath.path}"/>
2 comments:
Hi! With so little help available on the web for IBM MB, your blog is one of a kind. I have incorporated your idea of macrodefs in my BAR build script. Thanks!
Now, I have a question. There is a difference in the size of the BAR files created from the toolkit and using mqsicreatebar. It is in the flow.cmf file. The message flow uses multiple .msgmap and .esql files. Any idea what could causing the difference?
Post a Comment