[GRADLE-3248] [cpp plugin] 2.3 reports UP-TO-DATE after compilation error Created: 25/Feb/15 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Gradle Forums | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 0 |
Description |
Hi everyone Using the cpp plugin, if I clean, then build twice with a compilation error in a cpp, it reports the error both times. Here's my build.gradle apply plugin: 'eclipse' version = '1.0' model { and here's --debug from the final build that thinks it's up to date 12:57:35.673 [INFO] [org.gradle.BuildLogger] Tasks to be executed: [task ':compileMainExecutableMainCpp', task ':linkMainExecutable', task ':mainExecutable', task ':assemble', task ':check', task ':build'] Thanks Keith |
Comments |
Comment by Gradle Forums [ 25/Feb/15 ] |
Keith, What I was able to reproduce was the following: $ gradle clean build This is definitely a bug, but I was able to reproduce it with every version going back to 1.10 (did not try it for versions beyond that), so it doesn't look like this is a 2.3 regression, but something that's been there for a while. I'll open up a JIRA ticket for it and we'll take a look at it. |
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. |