ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18398] - Sometimes the <parellel> task may lead to fail
Date Thu, 27 Mar 2003 08:09:55 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18398>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18398

Sometimes the <parellel> task may lead to fail

bodewig@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From bodewig@apache.org  2003-03-27 08:09 -------
If I'm reading this correctly, all spawned Ant builds will use javac tasks, right?
And you are probably using Sun's javac and no external command.

The problem you see is that Sun's javac is not thread-safe (at least not in 
JDK 1.3) and can produce several bad results.  I used to have a bookmark to
a couple of bugparade entries that showed that, but have lost them.  If you
go to the JDC and search for javac and thread, you'll find a lot of problems.

To solve your problem, you will want to add fork="true" in at least two of your
three build files that get called in the parallel task.

Mime
View raw message