Humm now that brings up an interesting question. I see what your saying...
See the source tree is built up of many projects as well as a common
package for reused classes. So I would then adopt a hybrid of those ideas
if I was to follow that I have 1 build.xml for each project. Since
projects
There's another thread that's been going on in this list that goes over
the merits of having a "global" build where a single build.xml file
builds everything versus a "local" build where each package has its own
build.xml file and the whole thing is driven by a global build.xml
which is essentiall
Ok so from what I gather then I am using them the way you are too... It
just felt rather strange and like ANT was trying to move toward a scripting
language and not XML tags...
here is an simplified example of what I was talking about with the
functions:
Only to check if a property exists. Your tags are fine, they'll make
those if attributes readable!
--- Benjamin Russell Stocum <[EMAIL PROTECTED]> wrote:
> In the Target tag, does the "if" attribute allow you to have a logic
> expression, or does it just allow one to check to see if a "property"
Diane Holt wrote:
>
> --- Benjamin Russell Stocum <[EMAIL PROTECTED]> wrote:
> > In the Target tag, does the "if" attribute allow you to have a logic
> > expression, or does it just allow one to check to see if a "property"
> > exists?
>
> Just if/unless the property is set. If you need to test
--- Benjamin Russell Stocum <[EMAIL PROTECTED]> wrote:
> In the Target tag, does the "if" attribute allow you to have a logic
> expression, or does it just allow one to check to see if a "property"
> exists?
Just if/unless the property is set. If you need to test for a value, you
can either modif
