[GRADLE-1508] gradle occasionally leaves stale .class Created: 03/May/11  Updated: 16/Jan/17  Resolved: 16/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Duplicate Votes: 2


 Description   

Say the user deletes some .java file. After running gradle build the corresponding .class should be removed from classes ouput directory. Apparently it does not work occasionally.



 Comments   
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:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Martin Schaaf [ 15/Nov/16 ]

This sounds like a duplicate of issue GRADLE-2440

Comment by Benjamin Muschko [ 16/Jan/17 ]

I am going to close this issue as a duplicate. Please also see https://github.com/gradle/gradle/pull/1074 for more information.

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