Hmm I notice that the source is marked as experimental and subject to change. Is this still true? To what extent. I am slightly leary of upgrading to an alpha branch for our builds, particularly if the compelling feature is going to be a moving target :)

Also in your example buildfile, I am not sure I understand how the targets work. It looks like clean, build reversion and rebuild all do the same thing?

-Gus

Dominique Devienne wrote:
No doc, no test :-(

Subant accept a <buildpath>, which is a regular <path> (accepts nested
<fileset>, <dirset>, etc...

Subant's buildpath can be specified either outside (and referenced using
buildpathref) or inside (subant contains an implicit buildpath, so you can
add a <dirset> or <buildpathelement> directly within subant).

All files all the build path (it's a path, so it's ordered) that is a
directory is appended build.xml, or the value of the 'antfile' attribute if
specified. By default, subant calls the target it's defined within
automatically, or the target explicitly defined in the 'target' attribute.

Supports all <ant> attributes (except 'dir' and 'output') and nested
elements, and adds the 'failonerror' attribute, and nested
<fileset>/<filelist>/<buildpath>/<buildpathelement>/<dirset> elements to
compose the build path within.

Hope that helps. --DD

-----Original Message-----
From: Gus Heck [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 4:07 PM
To: Ant Developers List
Subject: Re: Ant task and dirset/fileset


Ok I searched bugzilla and subant appears exactly once... but it says it is committed. Problem is I don't see it in the manual, where can I get some doc for it? (or do I need to go find that link to the xdocs that I forgot to bookmark?)

-Gus

Dominique Devienne wrote:

Yes ;-) Me, and other people too. There is in Ant's BugZilla one task

called

<subant> that was recently added to the HEAD (slightly modified) on an
experimental basis, and there's also a patch to <ant> along the same

lines.

There has been quite a bit of discussion about both (one vs. the other

even)

on ant-dev as well. You should look it all up.

As the original author and user of <subant>, I can tell you it's working
just fine for me. Here's one of my build files, for example. Should be
familiar to Makefile writers (it does build C++ libraries after all ;-)

<?xml version="1.0"?>

<project name="Gocad" default="build">

 <taskdef resource="com/lgc/buildmagic/tasks.properties" />
 <typedef resource="com/lgc/buildmagic/types.properties" />

 <buildpath id="buildpath">
   <pathelement location="src/lib/utils/utils.xml" />
   <pathelement location="src/lib/math/math.xml" />
   <pathelement location="src/lib/geobase/geobase.xml" />
   <pathelement location="src/lib/lines/lines.xml" />
   <pathelement location="src/lib/surfaces/surfaces.xml" />
   <pathelement location="src/lib/volumes/volumes.xml" />
   <pathelement location="src/lib/tgobjs/tgobjs.xml" />
   <pathelement location="src/lib/appli/appli.xml" />
   <pathelement location="src/lib/ascii/ascii.xml" />
   <pathelement location="src/lib/archive/archive.xml" />
   <pathelement location="src/lib/gapi/gapi.xml" />
 </buildpath>

 <target name="clean">
   <subant buildpathref="buildpath" />
 </target>

 <target name="build">
   <subant buildpathref="buildpath" />
 </target>

 <target name="reversion">
   <subant buildpathref="buildpath" />
 </target>

 <target name="rebuild">
   <subant buildpathref="buildpath" />
 </target>

</project>

-----Original Message-----
From: Gus Heck [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 3:34 PM
To: [EMAIL PROTECTED]
Subject: Ant task and dirset/fileset


Has anyone ever thought about or tried to make the ant task accept a fileset or dirset? I have a use for such functionality but, before I go writing myself a custom version, or writing a patch, I thought I might ask if this has been tried, is being tried, or has be explicitly decided against?

-Gus

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





Reply via email to