Revision as of 05:10, 21 May 2007

< To: Buckminster Project

What has changed in this build?

• Ant actor API - Buckminster will no longer use Ant "fileset" references to pass requirement and products information to the Ant runtime. The main reason this was removed was that it caused problems when using <antcall> to call into the same file again. The <antcall>, altough it can pass references, assumes that all fileset declarations in a file are valid and cannot understand when filesets are passed by reference on from Java.

The only proper mechanism for passing data to Ant seems to be using properties. This is also the only possible way to do it using the platform ant-runner that we plan to shift to in a near future.

What you need to do

• If you have written your own actions that make use of an "ant" actor, please read up on the documentation of Ant actor API and make necessary changes to your scripts. Here are some examples:

Example using filesetgroup

If you used the buckminster.filesetgroup and you used to write:

<buckminster.filesetgroup refid="some.name.filesetgroup"/>

Replace it with:

<buckminster.filesetgroup value="${fs:some.name}"/>

Example using singleton

If you used to rely on buckminsters ability to pass singleton prerequisites or products in a property and wrote things like:

<mkdir dir="${some.singleton}"/>

Replace with:

<mkdir dir="${sp:some.singleton}"/>

Example using fileset

If you used a property that appointed a folder containing one single file that you don't know the name of and want it expanded and wrote things similar to:

<pathconvert property="input.file">
    <path>
        <fileset dir="${requirement}" includes="*.zip"/>
    </path>
</pathconvert>

Replace with:

<buckminster.valuefileset value="${fs:requirement}" id="requirement.fileset"/>
<pathconvert property="input.file">
    <path>
        <fileset refid="requirement.fileset"/>
    </path>
</pathconvert>