easy_app_helper 2.1.0 → 2.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 0352ee0a8fcd905f3078f99d49ec0d0f1e760b4f
-  data.tar.gz: aa425b6c080f4b007e0b8eb21aa2d4871008a2ac
+  metadata.gz: 1168a6f995f114abeab0b51069258d491692cd8e
+  data.tar.gz: 6080ffe247cd5f60b3338a5a15864c38c67c73bf
 SHA512:
-  metadata.gz: 0fd9cd9cbc19b33177d7d26f89670bff03ee4fa5317adec804e5c7144230ee7d64e6fa854d165dfedee49fd149218e8b806eeb292ca7e968adb94ee8931be35f
-  data.tar.gz: 1cad685afd543aecab65bb53b24befd86af6d3c632e21a6ea23a36c3fa2968a92e214a9221af9bdc7a36bc75aaf0033e4cc752376bfc8022ffbbbc306efdba3b
+  metadata.gz: d3e694dbe8f1f50a2336a1210b65194490f4010ba36b724456af600a13de2ee3ea94bf3f295705b1b95670f0b36f9f013bd39b5dd34836424e2705416830a29b
+  data.tar.gz: 1300bb54399655db63681ec5f8ac793773706ed30b7ff012f15917f17064b473036060c98b0f6969978bdd9ef998443d48592a460f3f75aec5c5a76cd9999f6a

data/README.md

@@ -202,7 +202,7 @@ The two [easy_app_helper][EAH] tasks are quite self-explanatory.
 
 Basically you will do a:
 
-    $ bundle rake easy_app_helper:create_executable
+    $ bundle exec rake easy_app_helper:create_executable
 
 And it will reply something like:
 
@@ -211,7 +211,7 @@ File '/home/you/devel/ruby/gems/your_gem/bin/your_gem' created with execution ri
  -> Try: "bundle exec '/home/you/devel/ruby/gems/your_gem/bin/your_gem' --help"
 ```
 
-It means that by default, the rake task will create a executable with the name of the gem you are currently developing.
+By default, the rake task will create a executable with the name of the gem you are currently developing.
 __This task is safe and will never overwrite an existing file__. Instead, if the file already exists, you would get:
 
 ```
@@ -222,8 +222,8 @@ File '/home/you/devel/ruby/gems/your_gem/bin/your_gem' already exists !
 You can, of course, specify your own file name to the rake task. Depending on your shell, and due to different
 variable expansion mechanisms, you have to do it differently:
 
-* __zsh__ should be something like: `bundle rake easy_app_helper:create_executable\[my_executable\]`
-* whereas in __bash__ more probably: `bundle rake easy_app_helper:create_executable[my_executable]`
+* __zsh__ should be something like: `bundle exec rake easy_app_helper:create_executable\[my_executable\]`
+* whereas in __bash__ more probably: `bundle exec rake easy_app_helper:create_executable[my_executable]`
 
 Check the documentation of your shell for further information.
 You should nevertheless have this kind of answer from the task:
@@ -234,7 +234,7 @@ File '/home/you/devel/ruby/gems/your_gem/bin/my_executable' created with executi
 ```
 
 You can notice the slight changes in terms of code in the two generated scripts ;-). Check the template with
-`bundle rake easy_app_helper:show_template` to understand how the template adapts.
+`bundle exec rake easy_app_helper:show_template` to understand how the template adapts.
 
 
 ## Complete example of a script based on `easy_app_helper`

data/lib/easy_app_helper/version.rb

@@ -1,3 +1,3 @@
 module EasyAppHelper
-  VERSION = '2.1.0'
+  VERSION = '2.1.1'
 end

data/test/foo/Rakefile

@@ -1,8 +1,6 @@
 puts 'In the Test Gem'
 require 'bundler/gem_tasks'
 
-require 'easy_app_helper'
-
 spec = Gem::Specification.find_by_name 'easy_app_helper'
 load "#{spec.gem_dir}/Rakefile"
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: easy_app_helper
 version: !ruby/object:Gem::Version
-  version: 2.1.0
+  version: 2.1.1
 platform: ruby
 authors:
 - L.Briais