[GRADLE-2800] Checkstyle plugin does not support reading config file from classpath or via URL Created: 20/Jun/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1


According to [1]http://checkstyle.sourceforge.net/ant... the Checkstyle task can take a config attribute which can be a file, BUT it also can be a relative location which it'll lookup using ClassLoader.getResource(). The Gradle checkstyle task though enforces that the input be a real file.

Additionally the checkstyle task (via Ant) supports a URL, and Gradle does not expose it that field or possibility.

[1] http://checkstyle.sourceforge.net/anttask.html

Comment by Youri Bonnaffé [ 01/Jan/14 ]

I would like to work on this issue but the requirements are not clear to me.
My use case is to share a common checkstyle configuration via a JAR file, put as a classpath dependency in my build and use it in the checkstyle configuration.

Currently, configFile is a mandatory attribute for Checkstyle plugin, I would suggest to make it optional, add a new attribute configURL and use it if it set instead of configFile.

What do you think?

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