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=26560>. 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=26560 Ant build breaks into seemingly infinite loop Summary: Ant build breaks into seemingly infinite loop Product: Ant Version: 1.6.0 Platform: PC OS/Version: Windows XP Status: NEW Severity: Blocker Priority: Other Component: Core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] ***IMPORTANT NOTE:************************************************* The build in question works perfectly fine on a comparable XP box. The only difference between the two environments is that the environment in which the build works is on a Compaq EVO desktop and the environment in which the build does not work is on a HP Compaq nx9010 laptop. Both are Windows XP (env var reports that OS = WINDOWS_NT) and both were running same versions of Java and Ant. This has been tried with both Ant 1.5.4 and 1.6, with no improvement. ********************************************************************* PROBLEM DESCRIPTION: The parent build file utilizes several other *.xml files to build the entire project. It starts off by successfully building several targets until it seems to kick into an infinite loop for some unknown reason (there is no error reported anywhere). It does this in the same place every time: ------------- ant output ----------------------------------------------- build.domain: compile.domain: [echo] Compiling c:\rpm_current\rpm\Domain... [javac] Compiling 3283 source files to C:\rpm_current\build\Server count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 <ad infinitum /> ------------- /ant output ---------------------------------------------- It goes ad infinitum - or seemingly - until it seems to 'catch' on something and then start building again, but it seems to have lost all references to the libraries defined in the <classpath> element, even though classes12.zip and quartz1.2.3 are both included in the classpath - it also reports this for all EJB and JMS stuff, anything which requires an imported library - these two entries are ONLY an example, it scrolls on for quite a while: ------------- ant output ----------------------------------------------- count = 0, total = 477 count = 0, total = 139 [javac] C:\rpm_current\rpm\Domain\<deletedForIntellectualPropertyReasons>.java:103: package oracle.jdbc does not exist [javac] import oracle.jdbc.OraclePreparedStatement; [javac] ^ count = 0, total = 477 count = 0, total = 139 [javac] C:\rpm_current\rpm\Domain\<deletedForIntellectualPropertyReasons>.java:4: package org.quartz does not exist [javac] import org.quartz.Job; [javac] ^ ------------- /ant output ---------------------------------------------- The build finally ends with these errors: ------------- ant output ----------------------------------------------- <scrolling for 100's of entries before getting here> count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 count = 0, total = 477 count = 0, total = 139 [javac] Note: C:\rpm_current\rpm\<deleted for intellectual property reasons>.java uses or overrides a deprecated API. [javac] Note: Recompile with -deprecation for details. [javac] 100 errors build.xml:323: Following error occured while executing this line build.xml:203: Following error occured while executing this line build.xml:129: Following error occured while executing this line build.xml:79: Following error occured while executing this line domain.xml:98: Compile failed; see the compiler error output for details. ------------- /ant output ----------------------------------------------- The interesting thing is to look at line 98 of domain.xml: ------------- domain.xml ----------------------------------------------- <target name="compile.domain"> <echo message="Compiling ${work.dir}\Domain..."/> <!-- <mkdir dir="${build.dir}/Domain"/> --> <javac classpathref="classpath.compilation.domain" srcdir="${work.dir}/Domain" destdir="${build.dir}/Server" debug="on"/> LINE 98 --> <!-- destdir="${build.dir}/Domain"/> --> </target> ------------- /domain.xml ---------------------------------------------- Where work.dir and build.dir are defined in the parent build.xml. My guess is this may be a manifestation of the infinite loop problem, similar to losing the classpath - it is also losing the ant variables. Why this occurs on one XP box and not the other is baffling to me. The source is checked out from CVS, the same repository, the same version, the same time, and every time it works on one and not the other. It has been seriously aggravating me for over a month now. I have to go to other developers and ask them to check out and build for me to see if my changes don't break the build. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
