{"action":"created","issue":{"url":"https://api.github.com/repos/causes/scss-lint/issues/372","labels_url":"https://api.github.com/repos/causes/scss-lint/issues/372/labels{/name}","comments_url":"https://api.github.com/repos/causes/scss-lint/issues/372/comments","events_url":"https://api.github.com/repos/causes/scss-lint/issues/372/events","html_url":"https://github.com/causes/scss-lint/pull/372","id":58416025,"number":372,"title":"Add a new CheckStyle formatter","user":{"login":"Sweetchuck","id":591103,"avatar_url":"https://avatars.githubusercontent.com/u/591103?v=3","gravatar_id":"","url":"https://api.github.com/users/Sweetchuck","html_url":"https://github.com/Sweetchuck","followers_url":"https://api.github.com/users/Sweetchuck/followers","following_url":"https://api.github.com/users/Sweetchuck/following{/other_user}","gists_url":"https://api.github.com/users/Sweetchuck/gists{/gist_id}","starred_url":"https://api.github.com/users/Sweetchuck/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Sweetchuck/subscriptions","organizations_url":"https://api.github.com/users/Sweetchuck/orgs","repos_url":"https://api.github.com/users/Sweetchuck/repos","events_url":"https://api.github.com/users/Sweetchuck/events{/privacy}","received_events_url":"https://api.github.com/users/Sweetchuck/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-02-20T21:56:20Z","updated_at":"2015-02-25T23:04:32Z","closed_at":"2015-02-25T18:05:13Z","pull_request":{"url":"https://api.github.com/repos/causes/scss-lint/pulls/372","html_url":"https://github.com/causes/scss-lint/pull/372","diff_url":"https://github.com/causes/scss-lint/pull/372.diff","patch_url":"https://github.com/causes/scss-lint/pull/372.patch"},"body":"I have not found any Jenkins plugin which is suitable to process an XML which is generated by the `--format=XML` option.\r\n\r\nThis new formatter/reporter almost the same as the XML formatter only difference is that this produce a standard Checkstyle format.\r\n"},"comment":{"url":"https://api.github.com/repos/causes/scss-lint/issues/comments/76080951","html_url":"https://github.com/causes/scss-lint/pull/372#issuecomment-76080951","issue_url":"https://api.github.com/repos/causes/scss-lint/issues/372","id":76080951,"user":{"login":"sds","id":677877,"avatar_url":"https://avatars.githubusercontent.com/u/677877?v=3","gravatar_id":"","url":"https://api.github.com/users/sds","html_url":"https://github.com/sds","followers_url":"https://api.github.com/users/sds/followers","following_url":"https://api.github.com/users/sds/following{/other_user}","gists_url":"https://api.github.com/users/sds/gists{/gist_id}","starred_url":"https://api.github.com/users/sds/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sds/subscriptions","organizations_url":"https://api.github.com/users/sds/orgs","repos_url":"https://api.github.com/users/sds/repos","events_url":"https://api.github.com/users/sds/events{/privacy}","received_events_url":"https://api.github.com/users/sds/received_events","type":"User","site_admin":false},"created_at":"2015-02-25T23:04:32Z","updated_at":"2015-02-25T23:04:32Z","body":"I apologize--that documentation is clearly incorrect.\r\n\r\nWhen the XML formatter was first added (it was actually the first pull request to `scss-lint`; see PR #1) we merged it without verifying the author's claim that it was intended to be consumed by Jenkins. Thus we included it in the documentation without confirming ourselves that it was \"useful\". It has stuck around ever since.\r\n\r\nI've removed the confusing documentation in 8ea0292f234610079e0a00a0f036089e19ed5a6d. You'll have to talk to @volpino to understand how he is using it with Jenkins.\r\n\r\nNow let me explain why I don't want to merge this into the main `scss-lint` project.\r\n\r\nBy merging this, we are setting a precedent that `scss-lint` directly supports third-party tools (like the CheckStyle Jenkins plugin). This is _not_ a claim we as a maintainer of the gem want to make. As we don't use the CheckStyle plugin internally, we can't promise to ensure it's well-tested and functional.\r\n\r\nThus the approach we suggest is that some other party (e.g. yourself) take the file `lib/scss_lint/reporter/checkstyle_reporter.rb`, place it into a separate gem, and then distribute that gem. We will happily include a link to it in our documentation. Anyone can then use the formatter by passing the `--require=scss-lint-checkstyle-reporter --format=Checkstyle` flags to `scss-lint`. This provides a clean way for reuse while relieving us the burden of maintenance. This is a style that many open source projects use (see the [Atom Linter](https://atom.io/packages/linter) project as an example).\r\n\r\nThese are the sorts of decisions any large open source project needs to make. I'm sorry if this seems unfair, but I believe it's in the best interest of the project."}}