[GRADLE-2273] Log level changes do not work with the daemon Created: 03/May/12 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 1.0-rc-3 |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Ingo Kegel | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 7 |
Issue Links: |
|
Description |
In order to display the output of ant tasks, I temporarily change the log level to INFO by calling logging.level = LogLevel.INFO. Without the daemon, all output from the ant task is printed on the console. When the daemon is used, the output is not printed on on the console, only in the daemon log file. |
Comments |
Comment by Charlie Groves [ 19/Feb/14 ] |
I just spent 30 minutes following advice like http://stackoverflow.com/questions/11413559/how-do-i-intercept-or-elevate-log-messages-when-calling-an-ant-task-from-gradle and wondering why it didn't work for me. It'd be lovely to have this fixed. |
Comment by Endre Stølsvik [ 24/Feb/14 ] |
Same here: I need the output of ant.java, and by default it disappears. When I /finally/ found the logging.level, I lit up with hope - but it is useless in the daemon (i.e. inside Eclipse). |
Comment by Joseph Docksey [ 11/Mar/16 ] |
It would be great to have this fixed for our team as well. |
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. |