[GRADLE-3043] Tasks with public fields can't be annotated with @InputFile/@OutputFile/... Created: 12/Mar/14  Updated: 24/Jan/17  Resolved: 24/Jan/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: 1


Assigning input/output file annotations to public fields will not make the fields be inputs/outputs, when there are no getters defined, as below.

class MyTask extends DefaultTask {

public File outputFile

public FileCollection inputFiles

def doSomething() {
// ...

It would be very helpful if Gradle at least could fail the build when/if this is detected.

Removing the "public" keyword from the field declaration will make everything work as expected.

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 [ 24/Jan/17 ]

IMHO public fields are a Java anti-pattern and shouldn't be used. We are not going to implement a fix for the issue.

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