If you are using the ant command-line script then it's setting a
classpath before it invokes ant's main class. This classpath likely
includes the rt.jar you are trying to avoid, a bad idea if you ask me. I
would downgrade my JDK before I removed classes from rt.jar or moved
another jar in front of
I generally define macrodef under project but it's also legal under
target. Where you put the definition defines the scope of the macro. If
you so choose, you can define macros in a project by themselves and use
the import task to pull them into the current build file. Import and
macros are a power
A macrodef can pretty much include any other ant task between its
sequential tag. Below is an example from the docs showing the macro
definition and a call to the macro. Pay close attention to the
tag and replace it with a tag named and you
get the general idea of a macro. When the macro is exec
If you are using 1.6.x, define a macro using macrodef and call the macro
with each file. I used a similar approach to automate xdoclet tasks for
different groups of files.
Grant
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For ad
Stefan Bodewig wrote:
> On Mon, 08 May 2006, Grant Lewis <[EMAIL PROTECTED]> wrote:
>
>> In my child project I have the following path definition:
>>
>>
>>
I'm not having much luck with in version
1.5.4. I'm stuck using 1.5.4 because a weblogic ant task used in my
build process requires 1.5.4 so I can't upgrade to the latest release.
In my parent script I define a path element like the following:
I then have a target definition that i
