[GRADLE-1230] compileJava and compiler warnings console output Created: 23/Nov/10  Updated: 01/Feb/17  Resolved: 01/Feb/17

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

Type: Bug
Reporter: Spencer Allain Assignee: Unassigned
Resolution: Duplicate Votes: 6

Attachments: Zip Archive dumb_terminal_example.zip    

 Description   

There is a missing newline after compileJava tasks writing to a console that messes up compiler warning parsers, like in Hudson.

:testProject:compileJava/home/hudson/jobs/TestJob/workspace/Test.java:23: warning [serial] serializable class Test has no definition of serialVersionUID

The "file" gets treated as :testProject:compileJava/home/hudson/jobs/TestJob/workspace/Test.java which clearly isn't correct.

This worked fine under 0.9-rc-1, which had a newline before any output from the task.

 Comments   
Comment by Luke Daley [ 23/Jan/13 ]

This was fixed some time ago.

Comment by Spencer Allain [ 23/Jan/13 ]

This is still a problem in 1.4-rc2. Probably the phrase "dumb terminal" should have been used instead of console.

Using the attached example with the below environment settings under unix with a bash shell demonstrates the problem:

export TERM=dumb
gradle

When running without an interactive console, such as within Jenkins, the newline is not there, so you still get the warnings attached directly to the end of the lifecycle task information:

:project:compileJava/path/to/offending/file
:project:javadoc/path/to/offending/file

Comment by Spencer Allain [ 23/Jan/13 ]

Run with export TERM=dumb to demonstrate actual issue. Should have provided this example back in 2010.

Comment by Luke Daley [ 23/Jan/13 ]

Thanks for the info, reopened.

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 Rowan Lonsdale [ 15/Nov/16 ]

This issue till exists in 2.14.1. PLease could it be migrated to GitHub. Thanks.

Comment by Benjamin Muschko [ 26/Jan/17 ]

@Rowan Does this issue also occur with the latest version of Gradle, 3.4? Would you mind opening the issue on GitHub if it is still the case?

Comment by Rowan Lonsdale [ 30/Jan/17 ]

Hi @Benjamin,

This issue still exists. I've raised issue 1275 on GitHub, and included a link to a Gist with a minimum project that reproduces the problem.

Thanks,
Rowan

Comment by Benjamin Muschko [ 01/Feb/17 ]

@Rowan Thanks for creating the issue.

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