[GRADLE-1534] Annotation to mark properties Created: 12/May/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Marco Hunsicker Assignee: Unassigned
Resolution: Won't Fix Votes: 0


It would be nice if Gradle would allow one to mark property fields or methods with an annotation instead of relying on a common naming convention.

When writing a commercial plugin, you probably want to apply obfuscation, and having to stick with a naming scheme a) just complicates the whole process and b) means some methods cannot be renamed. An annotation to mark properties would solve both issues nicely. Another advantage would be that one could name elements differently from the actual task/properties. Currently they must be the same.

class SimplePluginConvention {
private Foo foo;

public Foo getFoo)

{ return foo; }

public void setFoo(Foo rFoo)

{ foo = rFoo; }



class SimplePluginConvention {
private boolean compile;

public boolean isCompile)

{ return compile; }

public void setCompile(boolean rCompile)

{ compile = rCompile; }


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 11:57:56 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.