ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 48876] New: ANT_CMD_LINE_ARGS are rippling through lower level Ant usage
Date Tue, 09 Mar 2010 11:21:05 GMT

           Summary: ANT_CMD_LINE_ARGS are rippling through lower level Ant
           Product: Ant
           Version: 1.8.0
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: major
          Priority: P2
         Component: Wrapper scripts

Created an attachment (id=25110)
 --> (
Test Case

There was a section of code removed from the ant.bat file in 1.8.0 that is
having a negative effect on some of our build scripts and processing.

The section of code is:
  if ""%1""=="""" goto doneStart
and existed on line 62 of the bat file.

The failing scenario in Ant 1.8.0 is:
We have a top level build file that uses <exec> to call into a Windows batch
file that in turn is using Ant.
We are noticing that the exec call and usage of ant in the lower level batch
script is being passed any arguments given to the top level file and in turn
failing with a message like:

Target "exec" does not exist in the project "a".

We have put together the attached test case to signify this behavior and have
tested it through 1.6.x, 1.7.x and can confirm that this behavior is new to

The test case uses a build.xml to exec a script file which in turn calls an
Running the test case like:
ant exec
causes the error message Target "exec" does not exist in the project "a".

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

View raw message