Could you add a jira issue for this? We should at least give you a decent error message telling you what the problem is.
On 26/02/2011, at 3:58 AM, Spencer Allain wrote: > For the real code I'm not longer overwriting the existing environment > variables. > > For my test case, I was just curious to see if things would work by setting > selective ones like TEMP, to hopefully easily find out what the underlying > dependencies really are. :-) Simply curiosity. > > -Spencer > > --- On Fri, 2/25/11, Peter Niederwieser <[email protected]> wrote: > > From: Peter Niederwieser <[email protected]> > Subject: [gradle-user] Re: Strange junit test exceptions > To: [email protected] > Date: Friday, February 25, 2011, 11:11 AM > > > > merscwog wrote: > > > > Nuking all of the normal environment variables proved to be fatal under > > windows. > > test { environment += ['FOO':'foo'] } works just fine. > > > > The preferred syntax for adding environment variables is either: > > environment(ONE: "one", TWO: "two") // can also be split into multiple > statements > > or: > > environment("ONE", "one") > environment("TWO", "two") > > > merscwog wrote: > > > > If I explicitly specify ['TEMP':'some_actual_directory'] then the JPA > > error goes away, but something else during the testing phase is clearly > > depending upon other environment variables, as I get this different error: > > > > Didn't you just say that you no longer nuke (nor change) the remaining > environment variables? > > -- > Peter Niederwieser > Developer, Gradle > http://www.gradle.org > Trainer & Consultant, Gradle Inc. > http://www.gradle.biz > Creator, Spock Framework > http://spockframework.org > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Re-Qi4j-moves-to-Gradle-tp3395500p3400344.html > Sent from the gradle-user mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
