Frank W. Zammetti wrote:
or you make every target conditional
unless="compile.disabled"
and then turn on and off on the command line
For the way I work, this isn't feasible... I don't use an IDE, I use
UltraEdit... I have a single keystroke that executes the script, and I
don't have the oppo
Besides macrodef, you need to get familiar with import too.
-Original Message-
From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 13, 2005 10:52 AM
To: Ant Users List
Subject: Re: Ant dependencies task
Hi again,
This did the trick, almost... there was one other
Sorry, the nested target element is available with Ant 1.6.3.
-Original Message-
From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 13, 2005 10:41 AM
To: Ant Users List
Subject: Re: Ant dependencies task
Hi Brian,
That didn't seem to work... I get:
BUILD F
till run with a single click. Also, it is still easy to
comment/uncomment that which you don't want run.
Ben
-Original Message-
From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
Sent: Monday, August 15, 2005 9:31 AM
To: Ant Users List
Cc: Ant Users List
Subject: Re: Ant depe
> or you make every target conditional
>
> unless="compile.disabled"
>
> and then turn on and off on the command line
For the way I work, this isn't feasible... I don't use an IDE, I use
UltraEdit... I have a single keystroke that executes the script, and I
don't have the opportunity to alter the
Frank W. Zammetti wrote:
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.
or you make every target conditional
unless
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
rote:
Another thing that may work is converting your get_dependencies target
to a macrodef.
-Original Message-
From: Dick, Brian E.
Sent: Friday, August 12, 2005 3:19 PM
To: Ant Users List
Subject: RE: Ant dependencies task
You can recode
as
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
Another thing that may work is converting your get_dependencies target
to a macrodef.
-Original Message-
From: Dick, Brian E.
Sent: Friday, August 12, 2005 3:19 PM
To: Ant Users List
Subject: RE: Ant dependencies task
You can recode
as
You can recode
as
-Original Message-
From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
Sent: Friday, August 12, 2005 2:54 PM
To: user@ant.apache.org
Subject: Ant dependencies task
Does anyone have any experience with this add-on?
http://
A series of antcalls is not an alternative to using the depends
attribute. These are 2 different things. The depends attribute is used
to determine the order in which targets should run within a project. An
antcall is used to create a new project that uses the same build file.
A new project obje
13 matches
Mail list logo
