logo       

RE: Environment variables: msg#00081

lang.groovy.user

Subject: RE: Environment variables

I must have been seeing things. I've just gone back and tried this again and
it didn't work in the previous version. God knows what I was looking at,

Kevin Jones
http://kevinj.develop.com


> -----Original Message-----
> From: jastrachan-ee4meeAH724@xxxxxxxxxxxxxxxx
> [mailto:jastrachan-ee4meeAH724@xxxxxxxxxxxxxxxx]
> Sent: 07 October 2004 08:39
> To: user-i9PBDF1N6cxnkHa44VUL00B+6BGkLq7r@xxxxxxxxxxxxxxxx
> Subject: Re: [groovy-user] Environment variables
>
> On 6 Oct 2004, at 18:19, Kevin Jones wrote:
> > I have some old-ish Groovy scripts that worked with a version of
> > Groovy from March. I downloaded beta 7 and two things
> stopped working.
> > The first is access to environment variables. I have a script that
> > looks like this:
> >
> > ant.copy(toDir: "${SYSTEMROOT}", file: "scripts\\mysql\\my.ini",
> > overwrite:true) {
> > filterset() {
> > filter(token: "DIR", value: "${mysqlhomedir}")
> > }
> > }
> >
> > In the 'March' groovy this works, in beta 7 it fails with an
> > IncompatibleClassChangeError (is this the only error Groovy
> throws :)
> > ) at
> > getGroovyObjectProperty. SYSTEMROOT is set by Windows to
> reference the
> > dir that windows is installed. I'll mention the other problem in
> > another email,
>
> Incidentally are you using the same JVM - its not a bug
> introduced by switching to Java 5 or anything like that is it?
>
> I didn't know we ever supported environment variables in scripts :)
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
>




<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise