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

*** shadow/2580 Wed Jul 11 10:01:10 2001
--- shadow/2580.tmp.10740       Wed Jul 11 10:01:10 2001
***************
*** 0 ****
--- 1,29 ----
+ +============================================================================+
+ | Property Becoming Unset After Antcall                                      |
+ +----------------------------------------------------------------------------+
+ |        Bug #: 2580                        Product: Ant                     |
+ |       Status: NEW                         Version: 1.3                     |
+ |   Resolution:                            Platform: All                     |
+ |     Severity: Normal                   OS/Version: All                     |
+ |     Priority: Other                     Component: Core tasks              |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: [EMAIL PROTECTED]                                   |
+ |  Reported By: [EMAIL PROTECTED]                                      |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ Using a sequence of antcall's and 'depends', a given property (set by the 
+ available task, on a file) becomes unset.
+ 
+ I have reproduced this bug, using Ant 1.3, on both Win2k and Solaris8.
+ 
+ I have an example build.xml file for reproducing the bug, but I can't find 
how 
+ to add files to a bug report. If you email me, I'll send you a jar containing 
+ the files to reproduce the bug (it seems to require multiple files, so I 
don't 
+ want to paste them all here). If you email me during work hours (9ish-6ish 
ET; 
+ this is a work email) I'll send the dealy to you immediately.
+ 
+ 
+ Thanks.

Reply via email to