Just out of curiosity, if gradle's location is derived from the system path, what would happen when gradle is invoked while not on the path?
I'm thinking about CI servers as a use case. Any CI server that has to support multiple versions of gradle for different builds would probably just invoke different gradle instances directly, wouldn't it? Sean On Mon, Jan 3, 2011 at 9:25 AM, Sean Reilly <[email protected]> wrote: > My team avoids the possibility of error by using the GRADLE_HOME > environment variable when setting the path: > > export PATH=$GRADLE_HOME/bin:$PATH > > Which is a fairly standard bash practice, imo. > > The change wouldn't really affect us. That being said, no reasons to keep > it come immediately to mind, either. > > Sean > > > On Mon, Jan 3, 2011 at 3:35 AM, Adam Murdoch <[email protected]> wrote: > >> Hi, >> >> I'd like to axe the $GRADLE_HOME environment variable. >> >> The reason is that you have to change both the PATH and GRADLE_HOME >> variables when you switch Gradle versions. This is prone to error, so that >> you end up using a version which you don't expect. >> >> You can achieve the same effect that GRADLE_HOME provides by messing with >> your PATH variable, so I think that GRADLE_HOME is just pointless >> complexity. >> >> Does anyone have a good reason to keep it? >> >> >> -- >> Adam Murdoch >> Gradle Developer >> http://www.gradle.org >> CTO, Gradle Inc. - Gradle Training, Support, Consulting >> http://www.gradle.biz >> >> >
