jshint4r 0.1.2.1 → 0.1.3

data/{README.md → README.rdoc}

@@ -1,29 +1,10 @@
-![https://travis-ci.org/wtnabe/jshint4r](https://travis-ci.org/wtnabe/jshint4r.png)
+{<img src="https://travis-ci.org/wtnabe/jshint4r.png" />}[https://travis-ci.org/wtnabe/jshint4r]
 
-# Jshint4r
+= jshint4r
 
-jshint runner for ruby ( with execjs )
+Description goes here.
 
-## Install
-
-    gem install jshint4r
-
-## How to use
-
-just type
-
-    jshint4r
-
-## Requirements
-
- * CRuby 1.8 or 1.9 ( maybe works for other implements )
- * JavaScript Runtime ( supported by execjs gem )
-
-## Bonus feature :-)
-
- * 'unsafechar' for shutting up 'Unsafe character' mode
-
-## Contributing to jshint4r
+== Contributing to jshint4r
  
 * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
 * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
@@ -33,7 +14,7 @@ just type
 * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
 * Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
 
-## Copyright
+== Copyright
 
 Copyright (c) 2011 wtnabe. See LICENSE.txt for
 further details.

data/VERSION

@@ -1 +1 @@
-0.1.2.1
+0.1.3

data/jshint4r.gemspec

@@ -5,17 +5,17 @@
 
 Gem::Specification.new do |s|
   s.name = "jshint4r"
-  s.version = "0.1.2.1"
+  s.version = "0.1.3"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["wtnabe"]
-  s.date = "2013-07-29"
+  s.date = "2013-01-24"
   s.description = "jshint runner for ruby"
   s.email = "wtnabe@gmail.com"
   s.executables = ["jshint4r"]
   s.extra_rdoc_files = [
     "LICENSE.txt",
-    "README.md"
+    "README.rdoc"
   ]
   s.files = [
     ".document",
@@ -24,7 +24,7 @@ Gem::Specification.new do |s|
     ".travis.yml",
     "Gemfile",
     "LICENSE.txt",
-    "README.md",
+    "README.rdoc",
     "Rakefile",
     "VERSION",
     "bin/jshint4r",
@@ -56,13 +56,14 @@ Gem::Specification.new do |s|
     "spec/spec_helper.rb",
     "spec/support/sample_error.rb",
     "vendor/jshint/CHANGELOG",
-    "vendor/jshint/README.markdown",
+    "vendor/jshint/Makefile",
+    "vendor/jshint/README.md",
     "vendor/jshint/jshint.js"
   ]
   s.homepage = "http://github.com/wtnabe/jshint4r"
   s.licenses = ["MIT"]
   s.require_paths = ["lib"]
-  s.rubygems_version = "1.8.24"
+  s.rubygems_version = "1.8.23"
   s.summary = "jshint4r"
 
   if s.respond_to? :specification_version then

data/lib/jshint4r/linter.rb

@@ -15,7 +15,7 @@ module JSHint4r
     # [return] Array or nil
     #
     def lint( target )
-      errors = context.call('JSHINT.run', File.read(target).toutf8, opts )
+      errors = context.call('JSHINT.run', File.read(target), opts )
       if errors
         errors = errors.compact
         errors = allow_unsafe_character(errors) if opts['unsafechar']

data/lib/jshint4r.rb

@@ -1,6 +1,4 @@
 require 'execjs'
-require 'yaml'
-require 'kconv'
 
 module JSHint4r
 end

data/vendor/jshint/Makefile

@@ -0,0 +1,23 @@
+build_dir:
+	@mkdir -p "build"
+
+rhino: build_dir
+	@echo "Building JSHint for Rhino"
+	@echo "#!/usr/bin/env rhino" > "build/jshint-rhino.js"
+	@cat "jshint.js" "env/rhino.js" >> "build/jshint-rhino.js"
+	-@chmod +x "build/jshint-rhino.js"
+	@echo "Done"
+
+test:
+	@echo "Running unit tests"
+	@expresso tests/unit/*.js
+	@echo "Running regression tests"
+	@expresso tests/regression/*.js
+
+cover:
+	@echo "Start coverage"
+	@tests/helpers/coveraje.js
+
+clean:
+	@echo "Cleaning"
+	@rm -f build/*.js && echo "Done"

data/vendor/jshint/README.md

@@ -0,0 +1,104 @@
+JSHint, A Static Code Analysis Tool for JavaScript
+==================================================
+
+JSHint is a community-driven tool to detect errors and potential problems in
+JavaScript code and to enforce your team's coding conventions.
+
+**IMPORTANT**:
+
+ * This README is for people who are thinking about contributing to JSHint. For general usage
+   please refer to [our website](http://jshint.com/).
+ * If you want to report a bug about the website, please go to the
+   [jshint/site](https://github.com/jshint/site/) repository.
+ * If you want to report a bug or contribute to our NPM package, please go to the
+   [jshint/node-jshint](https://github.com/jshint/node-jshint/) repository.
+
+Reporting a bug
+---------------
+
+To report a bug simply create a [new GitHub Issue](https://github.com/jshint/jshint/issues/new) and
+describe your problem or suggestion. We welcome all kind of feedback regarding JSHint including but
+not limited to:
+
+ * When JSHint doesn't work as expected
+ * When JSHint complains about valid JavaScript code that works in all browsers
+ * When you simply want a new option or feature
+
+Please, before reporting a bug look around to see if there are any open or closed tickets that
+cover your issue. And remember the wisdom: pull request > bug report > tweet.
+
+Submitting patches
+------------------
+
+The best way to make sure your issue is addressed is to submit a patch. GitHub provides a very
+nice interface--pull requests--for that but we accept patches through all mediums: email, issue
+comment, tweet with a link to a snippet, etc.
+
+Before submitting a patch make sure that you comply to our style. We don't have specific style
+guide so just look around the code you are changing.
+
+Also, make sure that you write tests for new features and make sure that all tests pass before
+submitting a patch. Patches that break the build will be rejected.
+
+**FEATURE FREEZE**: Please note that we currently have a feature freeze on new environments and
+styling options. The only patches we accept at this time are for bug fixes.
+
+Tests
+-----
+
+To run tests you will need to install [node.js](http://nodejs.org/) and
+expresso. You can install the latter with npm:
+
+    npm install expresso
+
+After that, running the unit tests is as easy as:
+
+    expresso tests/unit/*.js
+
+Attribution
+-----------
+
+Core Team members:
+
+ * [Anton Kovalyov](http://anton.kovalyov.net/) ([@valueof](http://twitter.com/valueof))
+ * [Wolfgang Kluge](http://klugesoftware.de/) ([blog](http://gehirnwindung.de/))
+ * [Josh Perez](http://www.goatslacker.com/) ([@goatslacker](http://twitter.com/goatslacker))
+
+Maintainer: Anton Kovalyov
+
+License
+-------
+
+JSHint is licensed under the same slightly modified MIT license that JSLint is.
+It stops evil-doers everywhere.
+
+JSHint is a derivative work of JSLint:
+
+Copyright (c) 2002 Douglas Crockford  (www.JSLint.com)
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the "Software"),
+to deal in the Software without restriction, including without limitation
+the rights to use, copy, modify, merge, publish, distribute, sublicense,
+and/or sell copies of the Software, and to permit persons to whom
+the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included
+in all copies or substantial portions of the Software.
+
+The Software shall be used for Good, not Evil.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+DEALINGS IN THE SOFTWARE.
+
+JSHint was forked from the 2010-12-16 edition of JSLint.
+
+Thank you!
+----------
+
+We really appreciate all kind of feedback and contributions. Thanks for using and supporting JSHint!