Take a look at filtering when you do a . In your files, you put
target strings like "@serverName@" and "@[EMAIL PROTECTED] Here's an example
from
one of my build.xml:
The sub-task does the replacement. It finds all the t
Why not use the "dest" parameter and have the two task compile
their code to two different directories. That way, when you run your
build.xml again, it doesn't have to recompile everything.
I always use the "dest" parameter of the task. I mainly do
this, so all code compiles into a special build
I was just wondering why the tar task has a kind of misleading error
message and how I would fix it or report it to be fixed.
Apparently, if the tar task cannot find any files to include in the
destination, it just reports that there is nothing to do, that the tar
file is up to date.
A pr
