ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriele Bodda" <>
Subject Headless Ant: problems with loggers and listeners
Date Fri, 02 Nov 2007 14:22:46 GMT
Hi all,

my name is Gabriele, I'm trying to automate my build process using
CruiseControl but I'm currently experiencing some critical problems with the
Ant command it generates.

Our project is developed using WebSphere Integration Developer (you know,
IBM-enhanced Eclipse), under Windows XP Professional.
My Ant script is quite standard, but it uses some of the custom tasks that
come inside the IDE plugins, such as "workspaceBuild" or "exportEar" .

I've read into the documentation that, in order to get access to the
resources required by this kind of build script, I need to configure CC to
start Ant externally via java. I have therefore written a customized
runAnt.bat, and from the logs I see that the complete command launched by CC
is this:

-cp "D:\Programmi\IBM\Rational\SDP\6.0\eclipse\startup.jar"
-data "D:\Temp\CC\checkout"
-lib D:\Programmi\CruiseControl\lib\cruisecontrol-antprogresslogger.jar
"-Dcvstimestamp=2007-11-01 21:29:04 GMT"
-buildfile build.xml build

Do you see anything wrong in it? The point is that it doesn't work, not only
when CC launches it, but also if I launch it manually (and this why I came
here looking for help...)
Moreover, it doesn't tell me anything useful to undestand what's wrong.

An important fact I'd like to point out to you is that everything works well
if I launch the same command without these parameters:

-lib D:\Programmi\CruiseControl\lib\cruisecontrol- antprogresslogger.jar

Does this tell you anything already, maybe a known problem or a common
In case not, please tell me what information you need to try to help me,
because I'm really short of ideas.

Thank you very much for your help,

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message