[GRADLE-1188] Gradle daemon caches current working directory Created: 26/Oct/10  Updated: 04/Jan/13  Resolved: 24/Nov/10

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 0.9-rc-3

Type: Bug
Reporter: Chris Beams Assignee: Hans Dockter
Resolution: Fixed Votes: 1



  1. kill any running daemon
  2. cd <multi-project-root-dir>
  3. ./gradlew build
  4. Notice everything works as expected, all subprojects build
  5. cd <multi-project-root-dir>/<subproject1-dir>
  6. ../gradlew build
  7. Notice that all projects build. This is unexpected; only the leaf node project should build.

This unexpected behavior is appears to be due to the Gradle daemon caching CWD the first time it's run. This amounts to an unusable experience, even within the same multi-project build.

For now, we're running with --no-daemon to avoid this.

It is also a problem when working across projects. Starting the daemon in project1 means that any gradle invocations from project2 will inadvertently trigger builds in project1 – not exactly what's expected.

Comment by Adam Murdoch [ 08/Nov/10 ]

This is fixed in master branch.

Generated at Wed Jun 30 11:49:13 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.