ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Devienne" <>
Subject RE: Shell problems with wild cards and sh vs. cmd
Date Fri, 27 Aug 2004 16:05:59 GMT
> From: Scott Stirling []
> So, turns out I had exactly the same issue using the <java> task to
> weblogic.jspc a while back, and I had to write two targets for it (I
> didn't use
> the optional task for good reasons), one for Windows, which is fast as
> hell, and
> one for other OSes, which is slow. The speed is the difference between
> looping
> over each folder of JSPs with JSPC, vs. processing a whole huge Web
> all at once.

Understanding why it's slow would be the right solution, no?
How do you do this looping?

> Anyway, this is a recurring issue now for me. We've tried using <exec>
> call
> java to call the javac class. This also does not work (the '*.java' is
> still
> taken as a literal on UNIX). I know we *install* JDK 1.1 on any and
> boxes
> that need to build this, but it would be so much slicker to just be
> to
> stick in this one project and not have any external deps.
> Plus, the
> issue affects use cases (as described with the weblogic.jspc tool).

*.java is interpreted by a shell. Use vmlauncher="false", or use a
<fileset> you <pathconvert>, or use <apply parallel="true">.

Can't say much more without further details. --DD

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message