warbler-exec 0.1.0 → 0.1.1

data/LICENSE.txt

@@ -0,0 +1,25 @@
+= warbler-exec
+
+warbler-exec is provided under the terms of the MIT license.
+
+warbler-exec (c) 2012 Joe Kutner
+
+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 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.

data/README.md

@@ -25,7 +25,21 @@ Then run Bundler the with `--binstubs` option, and use `warbler-exec` to run the
 
 Every time that `warbler-exec` runs, it extracts the WAR file. Don't expect it to be fast.
 
-# Roadmap
+## Wait! I need Ruby installed to run the Ruby in my WAR?
 
-It would be a lot easier if we didn't have to run Bundler with the `--binstubs` option.  Eventually, someone (probably the person writing this) will submit a patch to Warbler that gets around this.
+Yes, you'll need a Ruby runtime installed on your machine in order to run this Gem (even though it switches to the Ruby inside your WAR file).  There are a few reasons for this:
+
++  Gems are nice way to distribute tools (better than "go download this script from ...")
+
++  Ruby is more portable than Shell scripts (this tool works on Windows).
+
++  This tool can be run on MRI, and most environments have that already installed (especially if they are using Puppet or Chef for configuration management).
+
++  Eventually, this tool will support more advanced options; such as exploding the WAR file once and running multiple commands.  Use Ruby for this will be much nicer than the alternatives.
+
+## Roadmap
+
++  It would be a lot easier if we didn't have to run Bundler with the `--binstubs` option.  Eventually, someone (probably the person writing this) will submit a patch to Warbler that gets around this.
+
++  It would be better if we didn't have to extract the WAR file every time.  That's easy enough to do, but i'm not sure how it would look from the command line.  Would there be a special command to extract the WAR to a particular location? 
 

data/bin/warbler-exec

@@ -2,6 +2,7 @@
 
 require 'zip/zip'
 require 'tmpdir'
+require 'rbconfig'
 
 path_to_war = ARGV.shift 
 
@@ -14,13 +15,26 @@ Zip::ZipFile.open(path_to_war) do |zipfile|
   end
 end
 
-Dir.chdir(File.join(destination, "WEB-INF"))
-ENV["CLASSPATH"] = Dir["#{Dir.pwd}/lib/*.jar"].join(":")
+workdir = File.join(destination, "WEB-INF") 
+Dir.chdir(workdir)
+
+ENV["CLASSPATH"] = Dir["#{Dir.pwd}/lib/*.jar"].join(File::PATH_SEPARATOR)
 ENV["GEM_PATH"] = "#{Dir.pwd}/gems"
 ENV["GEM_HOME"] = "#{Dir.pwd}/gems"
 
-begin
-  Kernel.exec("java -Xmx512m -cp $CLASSPATH org.jruby.Main #{ARGV.join(" ")}")
+begin 
+  # the unix way is the default way
+  cmd = "java -Xmx512m -cp $CLASSPATH org.jruby.Main #{ARGV.join(" ")}"
+  
+  if /mswin/ =~ RbConfig::CONFIG["host_os"]
+    cmd = "java -Xmx512m -cp %CLASSPATH% org.jruby.Main #{ARGV.join(" ")}"
+    # work around http://jira.codehaus.org/browse/JRUBY-6994 which makes Kernel.exec forget about chdir
+    if defined?(JRUBY_VERSION) && JRUBY_VERSION < "1.7.1"
+      cmd = "cd #{workdir} & #{cmd}"
+    end
+  end
+
+  Kernel.exec(cmd)
 rescue Errno::EACCES
   puts "warbler-exec: not executable: #{ARGV.first}"
   exit 126
@@ -30,6 +44,6 @@ rescue Errno::ENOENT
 rescue ArgumentError
   puts "warbler-exec: exec needs a command to run"
   exit 128
-end
+end 
 
 

data/warbler-exec.gemspec

@@ -3,7 +3,7 @@ $:.push File.expand_path("../lib", __FILE__)
 
 Gem::Specification.new do |s|
   s.name        = "warbler-exec"
-  s.version     = "0.1.0"
+  s.version     = "0.1.1"
   s.platform    = Gem::Platform::RUBY
   s.authors     = ["Joe Kutner"]
   s.email       = ["jpkutner@gmail.com"]

metadata

@@ -1,68 +1,69 @@
---- !ruby/object:Gem::Specification 
+--- !ruby/object:Gem::Specification
 name: warbler-exec
-version: !ruby/object:Gem::Version 
-  prerelease: 
-  version: 0.1.0
+version: !ruby/object:Gem::Version
+  version: 0.1.1
+  prerelease:
 platform: ruby
-authors: 
-  - Joe Kutner
-autorequire: 
+authors:
+- Joe Kutner
+autorequire:
 bindir: bin
 cert_chain: []
-
-date: 2012-03-26 00:00:00 Z
-dependencies: 
-  - !ruby/object:Gem::Dependency 
-    name: rubyzip
-    prerelease: false
-    requirement: &id001 !ruby/object:Gem::Requirement 
-      none: false
-      requirements: 
-        - - ">="
-          - !ruby/object:Gem::Version 
-            version: 0.9.4
-    type: :runtime
-    version_requirements: *id001
+date: 2012-12-31 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: rubyzip
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: 0.9.4
+    none: false
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: 0.9.4
+    none: false
+  prerelease: false
+  type: :runtime
 description: This utility allows you to execute commands with the context of a Warbler WAR file
-email: 
-  - jpkutner@gmail.com
-executables: 
-  - warbler-exec
+email:
+- jpkutner@gmail.com
+executables:
+- warbler-exec
 extensions: []
-
 extra_rdoc_files: []
-
-files: 
-  - .gitignore
-  - README.md
-  - bin/warbler-exec
-  - warbler-exec.gemspec
+files:
+- .gitignore
+- LICENSE.txt
+- README.md
+- bin/warbler-exec
+- warbler-exec.gemspec
 homepage: https://github.com/jkutner/warbler-exec
 licenses: []
-
-post_install_message: 
+post_install_message:
 rdoc_options: []
-
-require_paths: 
-  - lib
-required_ruby_version: !ruby/object:Gem::Requirement 
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: !binary |-
+        MA==
   none: false
-  requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        version: "0"
-required_rubygems_version: !ruby/object:Gem::Requirement 
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: !binary |-
+        MA==
   none: false
-  requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        version: "0"
 requirements: []
-
 rubyforge_project: warbler-exec
-rubygems_version: 1.8.15
-signing_key: 
+rubygems_version: 1.8.24
+signing_key:
 specification_version: 3
 summary: Allows execution of commands from a Warbler WAR file
 test_files: []
-