can i reference external flex-config in flexunit ant task?

flexunit gurus,

i'm trying to figure out how to best specify the compiler arguments for the flexunit ant task in flexunit 4.1 beta 1.  from the documentation i see this sample flexunit usage:

<flexunit workingDir="${bin.loc}" toDir="${report.loc}"
haltonfailure="false" verbose="true" localTrusted="true">
<testSource dir="${main.src.loc}" />
<testSource dir="${test.src.loc}">
<include name="**/*Test.as" />
</testSource>
<library dir="${lib.loc}" />
</flexunit>

in this example, the source and library paths are explicitly listed.  in this simple example all the needed libraries reside within a single directory.

when i build my application, i use a custom flex-config.xml file, as the following snippet shows:

        <mxmlc file="${application.file}" output="${swf.debug.file}" debug="true" headless-server="${headless.server}">
            <load-config filename="${flex.config.file}" />
        </mxmlc>

in that custom flex-config.xml file i list all the build options (e.g. source dirs, library paths, theme, etc.) appropriate for building the application.  the libraries i reference are in a number of different directories (in general each 3rd party library is in a different directory).

in the flexunit task, i could individually reference all the same libraries that are in the flex-config.xml, but that'd be a pain to keep them in sync.  i suppose i also could parse the flex-config.xml to extract the library information and use that to populate the library argument.  really what i want to say in the flexunit task is "build all source and tests as indicated in flex-config.xml, then run the tests", perhaps with a syntax like the following:

<flexunit workingDir="${bin.loc}"  toDir="${report.loc}"
haltonfailure="false" verbose="true" localTrusted="true">

            <load-config filename="${flex.config.file}" />
<testSource dir="${test.src.loc}">
<include name="**/*Test.as" />
</testSource>

<library dir="${flexunit.lib}" />
</flexunit>

i'd rather keep the flex-config.xml file free of any test specific information, so ideally i'd specify the path to the flexunit swc's and the test path in the flexunit task (as in the above example).

is there support for such usage currently or planned for in the future?  recommendations on how best to accomplish my goal of not duplicating library information already present in a custom flex-config.xml?

thanks.

-mike