I certainly agree with the need for subprojects. We have several
sub-projects that are invoked from the within our primary build file.
And they worked just fine. "AntCall" is a great add as well.
We have a src dir that has serveral build files in it. The change in
property handling has certainly improved our lot here. Is it more
accurate to say that the "ant" task works off the "basedir" property and
not the directory that contains the your build file? Currently we set
the basedir to .. from the src tree. The build and src directories are
peers.
Thanks for your explanation for traversing upwards of the build
directory. It does make sense.
Thanks,
don.
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 12/18/00, 1:42:52 PM, Diane Holt <[EMAIL PROTECTED]> wrote regarding Re:
Change in the "ant" task from 1.1 to 1.2:
> I believe the change was primarily driven by the concept of having
> "subprojects". I was against the change initially, but have actually come
> to rely on it, as a compromise from the old "build-file in every subdir"
> approach, or having just one giganto build-file at the top of the tree
> (which turned out to be just too unwieldy to deal with, and, in a
> source-control environment could have meant any number of people trying
to
> edit the file at the same time, leading to lots of "resolves" needing to
> be done [something you try hard to avoid]). The approach I took still
> isn't optimal by any means, but it was the best I could manage with Ant
> for now.
> From what I understand, the idea is to turn this off for Ant1.3, and
> require a "-find" flag be specified if you still want that functionality.
> (In fact, I believe if you pick up a nightly, that will be the behaviour
> -- which is one reason I haven't picked one up for awhile now.)
> Diane
> --- Don Schaefer <[EMAIL PROTECTED]> wrote:
> > Folks,
> > The following is noted in the whatsnew.txt in the binary distribution:
> > Ant will now search for a file named build.xml in the parent directory
> > and above (towards the root of the filesystem) if you didn't specify
> > -buildfile and there is no build.xml in the current directory.
> > I was curious what drove this change. We have located all of our
> > targets
> > in the same directory as our build.xml. Why start with the parent. I
> > am
> > sure that there is sound reasoning for this. The task was working fine
> > for us till this change.
> > Thanks for your time,
> > don.
> =====
> ([EMAIL PROTECTED])
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Shopping - Thousands of Stores. Millions of Products.
> http://shopping.yahoo.com/
