[GRADLE-1296] Daemon Does Not Handle System Properties Created: 08/Jan/11 Updated: 04/Jan/13 Resolved: 31/Mar/11 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.9.1 |
| Fix Version/s: | 1.0-milestone-2 |
| Type: | Bug | ||
| Reporter: | Robert Fischer | Assignee: | Adam Murdoch |
| Resolution: | Fixed | Votes: | 0 |
| Description |
|
I pass some sensitive data to Gradle via system properties. Unfortunately, the daemon does not retain system properties from either when it starts up or when the build runs: I can't seem to get the property into Gradle at all. As a stop-gap solution, I'm moving from using system properties to environment variables. But for the long term, system properties should be supported by the daemon. |
| Comments |
| Comment by Adam Murdoch [ 12/Jan/11 ] |
|
How do you pass the system properties to Gradle? |
| Comment by Robert Fischer [ 12/Jan/11 ] |
|
-Dfoo=bar |
| Comment by Michael Migdol [ 13/Mar/11 ] |
|
I believe this is an issue in GrailsScriptRunner. When invoked via executeCommand (as I believe Gradle does), GrailsScriptRunner.processArgumentsAndReturnScriptName (which is what inserts the -D arguments into the system properties) does not get called. This method is only invoked from GrailsScriptRunner.main. I've opened http://jira.codehaus.org/browse/GRAILS-7348 to track. |