[GRADLE-2531] Changes to buildSrc directory are not always detected. Created: 23/Oct/12 Updated: 21/Sep/16 Resolved: 23/Jan/13 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Gradle Forums | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Issue Links: |
|
||||||||
| Description |
|
From forum post: To reproduce, write a build that is successfully using some code from buildSrc/src/main/java. Now rename buildSrc/src into buildSrc/foo. The build will still work as before. Delete buildSrc/build. Now the build will fail (correctly) because the code from buildSrc is missing. Rename buildSrc/foo back to buildSrc/src. Now the build will work again. |
| Comments |
| Comment by Luke Daley [ 23/Oct/12 ] |
|
I was able to confirm this with latest master (Gradle 1.3) |
| Comment by Gary Hale [ 21/Sep/16 ] |
|
Another manifestation of this issue is buildSrc being removed from VCS (perhaps to move it into a separate repository). In this case, other developers will pull changes, which will remove the sources, but the build directory (which is external to VCS) will remain and the previously built plugins will still be available on the buildSrc classpath. |