[GRADLE-3475] Gradle forks a process to determine environment variables on first build and when publishing Created: 07/Jun/16 Updated: 10/Feb/17 Resolved: 10/Feb/17
Through DefaultLocalMavenRepositoryLocator.parseLocalRepoPathFromMavenSettings() (from Gradle)
We end up calling DefaultSettingsBuilder.interpolate() (from maven-settings-builder.jar)
Which creates a new EnvarBasedValueSource, which uses OperatingSystemUtils to retrieve OS level environment variables. (from plexus-utils.jar)
On Windows, this runs "cmd.exe /c set" and on *nix, it runs "env". The set of environment variables is cached in EnvarBasedValueSource
Later versions of plexus-utils do not fork a process to get environment variables, so we could either upgrade plexus-utils, the Maven libraries, both or implement our own SettingsBuilder to read settings.xml.
|Comment by Benjamin Muschko [ 15/Nov/16 ]|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.
We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.
Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
|Comment by Benjamin Muschko [ 10/Feb/17 ]|
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.