I do it that way for two reasons mainly:
(1) Many times during development I need to have certain tasks disabled,
and sometimes what is enabled and disabled changes, and I find it easier
to comment out an antcall as shown.
(2) It's a little more explicit in my mind as to what is happening and
Frank W. Zammetti wrote:
Hi again,
This did the trick, almost... there was one other piece to the puzzle...
I had to add inheritRefs="true" to all the targets I antcall'd. So, my
main build target looks like:
why do you structure your build process this way
Hi,
I'm new to the mailing list, and have a question about compiling
deprecated classes. Is it possible, when compiling with Ant, to
arrange the compilation so that deprecated classes are not ignored
during the build?
>From what I've read, the Java compiler will ignore deprecated classes
when co
Hi again,
This did the trick, almost... there was one other piece to the puzzle...
I had to add inheritRefs="true" to all the targets I antcall'd. So, my
main build target looks like:
...and the get_dependencies is now:
Hi Brian,
That didn't seem to work... I get:
BUILD FAILED
The type doesn't support the nested "target" element.
Using Ant 1.6.1
Frank
Dick, Brian E. wrote:
You can recode
as
-Original Message-
From: Frank W. Zammetti [mailto:[EMAIL P
The use of the deprecated tag is to advise developers to use an
alternate method/class while still including the deprecated
functionality in your products for backwards compatibility. I suggest
if you don't want certain files in your build at all to mark them as
removed in your repository, thi
