[GRADLE-2571] Configuring compileJava with options.debug = true not having expected effect Created: 26/Nov/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-9
Fix Version/s: None

Type: Bug
Reporter: John Ferguson Assignee: Unassigned
Resolution: Won't Fix Votes: 0


I would like to compile my Java classes with

g <--- all debug info

However, when I use the default of true or set the debug option in Gradle:


{ options.optimize = true options.debug = true }

I never see -g on the command line which is the Java Compiler's setting for all.

So instead I have to do this:


{ options.optimize = true options.debug = true options.debugOptions.debugLevel = "source,vars,lines" }

I think I can get by with the work around, but in case it is still an issue. OR maybe I have it wrong and I need to set options.debugOptions to something else?

Comment by Adam Murdoch [ 26/Nov/12 ]

I believe this issue has been fixed already (see GRADLE-2197). Could you try a later version of Gradle?

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:25:33 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.