ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Chamness" <ma...@cacheware.com>
Subject RE: System Environment variables don't work
Date Thu, 17 May 2001 17:54:46 GMT
My mistake.  I have verified that the May 17th
release no longer exhibits this bug.

>From the description of the bug,
it seemed that a better fix was provided:

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

------- Additional Comments From Greg Fenton 2001-04-25 22:33 -------
Might I offer the following modification as opposed to the currently
implemented fix?  It handles the issue a little more directly.
I have used it successfully to handle multi-line ENV values "correctly".
---------------------------------------------------------------------

I was looking for that fix.

-mark



> -----Original Message-----
> From: Nico Seessle [mailto:nico@apache.org]
> Sent: Wednesday, May 16, 2001 11:55 PM
> To: ant-user@jakarta.apache.org
> Subject: Re: System Environment variables don't work
>
>
> ----- Original Message -----
> From: "Mark Chamness" <markc@cacheware.com>
> To: <ant-user@jakarta.apache.org>
> Sent: Thursday, May 17, 2001 12:19 AM
> Subject: RE: System Environment variables don't work
>
>
> > Try this build file:
> >
> > build.xml
> > ---------------------------------------------
> > <project name="test" basedir="." default="test">
> >         <property environment="env"/>
> >         <target name="test">
> >                 <echo message="test"/>
> >         </target>
> > </project>
> > ---------------------------------------------
> >
>
> Stil no problem.
>
> >
> org.apache.tools.ant.taskdefs.Property.loadEnvironment(Property.java: 248)
>
> Can you please verify that you are using one of the nightly
> builds? Line 248
> in the current version from CVS reads
>
> 247:                int pos = entry.indexOf('=');
> 248:                if (pos == -1) {
> 249:                    log("Ignoring: " + entry, Project.MSG_WARN);
> 250:                } else {
> 251:                    props.put(prefix + entry.substring(0, pos),
> 252:                              entry.substring(pos + 1));
> 253:                }
>
> It seems that substring can never be called with an index of -1,
> doesn't it?
>
> Nico
>


Mime
View raw message