You're post is too long to answer in detail and I don't have the time
these days to go back and forth with you, but I'll still make a few
observations.
First, your hierarchy seems wrong. Putting the build.xml, classes
output dir, etc... in the source tree feels wrong. It's much better to
stick to
y 18, 2005 3:57 PM
> To: Ant Users List
> Subject: RE: nontrivial dependencies
>
>
> - Rainer Noack wrote:
>
> > just a hint:
> > what's about 's if/unless attributes...
>
> Both and certainly have
> their uses. And I don't hesitate to use t
- Rainer Noack wrote:
> just a hint:
> what's about 's if/unless attributes...
Both and certainly have their uses.
And I don't hesitate to use them where it makes sense to do so. But I
haven't found that they really help much with managing dependencies or
other "tricky" aspects of our buil
Michael Cepek wrote:
[snip]
Our team needs to be able to use the following Ant targets from within
ANY of the top-level java package directories (xxx = one of these
package names: admin, db, controller, and util):
[snip]
We also need these targets: build-all, test-all, javadoc-all, and
clean-all.
Hi Michael,
just a hint:
what's about 's if/unless attributes...
BTW: How would you handle this in eclipse?
Cheers
Rainer
> -Original Message-
> From: Michael Cepek [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 17, 2005 11:17 PM
> To: user@ant.apache.org
I've been trying for a very long time now (many man-days) to create Ant
build scripts to handle our new corporate project.
I've been using Ant for over 3 years, and programming professionally for
over 25 years.
Despite all that, I cannot seem to get Ant to do what we need on this
project. I am b
