DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40992>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40992 ------- Additional Comments From [EMAIL PROTECTED] 2006-11-17 11:10 ------- (In reply to comment #8) > You are of course free to backport the changes yourself, if you think that will > reduce the cost to your project. Just find the SVN commit that fixed the bug, > apply it to a local copy of the 1.6.5 branch, rebuild and retest. You do have to > recognise that this is now a less-supported release, and unless you have all the > dependencies, bits of ant will be missing. > I'd recommend trying the upgrade, as now is the best time for regressions. You > can use the workaround I suggested too, namely 'dont inherit the environment' Thanks for the suggestion; might be a bit of overkill for a PL/SQL developer though :) Re: newenvironment=true, it's catch 22. At time of the process fork, I know only case insensitive names and values of the required evironment variables. But the set of the required variables is only a sub-set the set of the sufficient variables. To find and set the rest of the values, I need to know the exact variable names, 'cause the system treats the names as case insensitive, while ANT does not. Alas, the proposed solution does not work. Workaround in that case is to use external batch as a wrapper for ANT and clear variables that are known to belong to the "required set". -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
