mqsipackagebar includes unnecessary files - bloats bar size

Problem title
mqsipackagebar includes unnecessary files - bloats bar size
.
Problem description
WMBT 8.0.0.2

We had some Ant build scripts written to include specified files into a
bar. These scripts have been working for a few months now, no problems.
We explicitly did not create an 'Application' from our project. We
simply built the bar by including all the needed files, file-by-file,
and used command line like:

Code:
mqsipackagebar -w xyz -a zyx -o file1 file2 ... file49 file50 file51


Someone down the line in the source code control system converted the
Message Flows into an Application. Now, the mqsipackagebar fails with

Quote:
BIP1868W: Ignoring 'file1.esql', which is in application
''. Use the -k option to include the application.


We have thousands of xml files that make up test case payloads located
in a subdirectory of the project. We never want to include these xml
files in the bar files.

When putting the -k option in the mqsipackagebar command, the
mqsipackagebar scans the project and includes all files specified by

http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp?
topic=%2Fcom.ibm.etools.mft.doc%2Fbc31720_.htm

Quote:
By default files with only the following extensions are included in the
BAR file: .xsdzip, .tblxmi, .xsd, .wsdl, .dictionary, .xsl, .xslt, .
xml, .jar, .inadapter, .outadapter, .insca, .outsca, .descriptor, .php,
.idl, .map, .esql, .msgflow, and .subflow. You can specify the -i
option to include files with any extension.


which is incorrectly including also all the thousands of xml payload
files.


How to change the default behavior of mqsipackagebar so that xml files
in specific directories are not included, or specified subdirectories
are ignored?


This is a request for an APAR to mqsipackagebar that enables the
commandline tool to exclude certain failed or directories when using
the -k option on the commandline.

We need a way to scope the file inclusion. Simply including all files
inside the project filesystem is not desirable. There are files we want
to be included in the project filesystem so that they get recorded into
the version control on that project but we don't want to deploy those
thousands of XML files to the Broker.

We do not want to use mqsicreatebar. We must use mqsipackagebar and
need to deplouythe resulting bar file without manually breaking it
apart to remove the unnecessary files.

We realize that mqsipackagebar is operating as it is designed and are
asking for an APAR to assist us in scoping the file inclusion to the
right level.
.