[GRADLE-1034] Compilation failure when java source file is moved from source set's groovy or scala src dir to java src dir Created: 14/Jul/10 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.9 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Adam Murdoch | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 1 |
| Issue Links: |
|
||||||||
| Description |
|
For example, run gradle classes and then move a Java source file from src/main/groovy to src/main/java. Running gradle classes again will fail with a groovy compilation failure. Same thing happens when moving a Java source file from src/main/scala. A clean does not fix this. Can only be unstuck with gradle -C rebuild clean |
| Comments |
| Comment by Luke Daley [ 23/Jan/13 ] |
|
Is this still an issue? |
| Comment by Adam Murdoch [ 02/Feb/13 ] |
|
yes. |
| 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. |