physique 0.3.5 → 0.3.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,15 +1,15 @@
1
1
  ---
2
2
  !binary "U0hBMQ==":
3
3
  metadata.gz: !binary |-
4
- MzY3MGZmNzZjZjU2YmVlZTdiMDAxYzZhYzZiZDc5ZTY5NDFjZjNiMw==
4
+ MGQyMDIxYzljOWM2MmQ5ZDBlYTMzNWU3NmRkMDY5OWM0YmYyZmFhMw==
5
5
  data.tar.gz: !binary |-
6
- N2M3MjUyMDE4ZjMxM2JkZDNjYTZkMjM2Y2M3MzZhYWVhOTcyNjhmOA==
6
+ YzUyNmM1NzdiZjNmMjI1MTQ1YTBhMzBhOTgzY2RkOGUxNDNmNDEzYw==
7
7
  SHA512:
8
8
  metadata.gz: !binary |-
9
- N2I3Y2U3YjFiMDYwMWMxNzk1NjM4ZjEwMmFhNmUwNGYxZWU1ZmE1MDIwNTQz
10
- YTEwYzI2Y2NhZjQwYmFiMzg3ZTFkYzM0ZWM0MGUwMzYxZTMwOTEyYTE2M2Jj
11
- OTAwMDdkN2I1MGEzYjE4NmIxYjA2Zjk4ZTNlZTBhNjY1ZTk5OGE=
9
+ NjVhZTkxOGEzYjU0NDI0NjYwODJjZTYwNzdkNWE3OGU4NDEwZDY4ODAwYmI3
10
+ NWM0NTZjNmZjNjE2ZDU5YzRlYzFjZjgxMzE0MGEwOTU1ZGZiMDM2MTRhOGM2
11
+ NTM5Yjg4ZjFlNTkwNzViOGFlNzk0MDllZjMxYTI2YzczYzU2YjY=
12
12
  data.tar.gz: !binary |-
13
- Y2RlMDE5ZTUxMjQ4NDEzZTZlYTRlYTQyYTEyZjczMzVjNmE1YmY5YjUxYTVh
14
- NDA1NDYyYTNlNTRkNTBkNGQ1ZTNlYTE4ZjBmMzRiM2JkZDhhMzA3MGNjZWEw
15
- YTljN2E1MTVmMzliMjIxNmYzMGM5M2ViYjMzMDhlYjdkNGE4YTc=
13
+ MDE3YTM5NzQxNTBmYmIxYWI0OTVhODNkNDkyZWE0MTkxZTY5YmE0YTEzYmQz
14
+ MzcxM2E5MDRiOWMwODJiNmQwMzliMTdmNDg0MWFiYzMyM2VkNzYwN2M5NmYz
15
+ ZDdjZGMwYTY4MDllOGY0MjM5ZjUyODk4Y2IxYzZlMDgzM2UyZTA=
@@ -98,7 +98,7 @@ rake test # Run unit tests
98
98
 
99
99
  Look at all of our shiny database tasks!
100
100
 
101
- In case it wasn't obvious, all of the FluentMigrator tasks are prefixed with `db`. Here's a break down of each task does.
101
+ In case it wasn't obvious, all of the FluentMigrator tasks are prefixed with `db`. Here's a breakdown of what each task does.
102
102
 
103
103
  ### Basic Tasks
104
104
 
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- physique (0.3.4)
4
+ physique (0.3.5)
5
5
  activesupport (~> 4.1)
6
6
  albacore (~> 2.3)
7
7
  map (~> 6.5)
@@ -17,7 +17,7 @@ GEM
17
17
  minitest (~> 5.1)
18
18
  thread_safe (~> 0.3, >= 0.3.4)
19
19
  tzinfo (~> 1.1)
20
- albacore (2.3.15)
20
+ albacore (2.3.16)
21
21
  map (~> 6.5)
22
22
  nokogiri (~> 1.5)
23
23
  rake (~> 10)
data/README.md CHANGED
@@ -212,7 +212,7 @@ end
212
212
 
213
213
  #### Custom Configuration
214
214
 
215
- You can use any unit testing framework. You just need to provide a bit more configuration.
215
+ You can use any unit testing framework. You just need to provide a bit more configuration. This effectively just wraps the Albacore method for declaring a test runner.
216
216
 
217
217
  ```ruby
218
218
  s.run_tests do |t|
@@ -250,8 +250,8 @@ Physique::Solution.new do |s|
250
250
 
251
251
  # Metadata to be included in your Nuspec
252
252
  p.with_metadata do |m|
253
- m.description = 'Common libraries for crux applications'
254
- m.authors = 'Robert Scaduto, Leo Hernandez'
253
+ m.description = 'My Awesome Library'
254
+ m.authors = 'My Company, Inc.'
255
255
  end
256
256
  end
257
257
  end
@@ -130,7 +130,7 @@ module Physique
130
130
  end
131
131
 
132
132
  def all_octopus_app_tasks(task)
133
- @options.apps.map { |a| "#{task}:#{a.name}" }
133
+ @options.apps.map { |a| "#{a.name}:#{task}" }
134
134
  end
135
135
 
136
136
  def add_task_aliases
@@ -1,3 +1,3 @@
1
1
  module Physique
2
- VERSION = '0.3.5'
2
+ VERSION = '0.3.6'
3
3
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: physique
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.3.5
4
+ version: 0.3.6
5
5
  platform: ruby
6
6
  authors:
7
7
  - Robert Scaduto
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2015-02-23 00:00:00.000000000 Z
11
+ date: 2015-02-24 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: bundler