[GRADLE-2770] deprecation warnings should include file and line numbers Created: 07/May/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Task
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 5


In upgrading to gradle 1.6, I see there are new deprecation warnings, so I need to go into my scripts and improve things. It would really make it easier if the warning message included the file and line number where this occurred. Perhaps also the plugin if there was one. Otherwise it can be hard to tell if something needs to be changed in my gradle scripts or if the problem is in a plugin that I happen to be using. Not sure how hard this would be, but it would be very nice to have.

I did see this which is related:

Also, while it seems you all have done a good job with making the deprecation messages meaningful, it might be nice to provide a URL for more information. You already have more information in the release notes, like here:
so adding a url to the corresponding section shouldn't be too hard.

[1] http://forums.gradle.org/gradle/topics/how_can_i_find_the_usage_of_deprecated_gradle_apis
[2] http://www.gradle.org/docs/current/release-notes#deprecations

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 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.

Generated at Wed Jun 30 12:31:02 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.