git_compound 0.1.1 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 8db5466d0de881b83ca8d78cfbc1350bd93fe7c9
-  data.tar.gz: 39b0313d49ad5c93eb070249c38cd625c844575c
+  metadata.gz: 3fcf9e29c1abe4d4c3fe2287e8559cd84035b8a7
+  data.tar.gz: b2746150e9f9fc1dfe86a5a12287606a85411302
 SHA512:
-  metadata.gz: a99ef50db20399145c1c2fd42505ac01e419a18959539379eeaf5b0a1860b44c576626896483e7371d396a3afc0a4760da0aa40cfc82dad2a4d02a15b043d2a7
-  data.tar.gz: b9ec8115fa1839dfa4f2f3187ce4abfd215678331d100c70b8e21b7e7fd25300d6a255f0e1c7228d34dc45def26001c1a6c81421bccde70f17ae6492c637aad3
+  metadata.gz: d0ab07e4b756841e02a71a62043bc67292a6de43b6e8c2abc811c0b6cf05c9f3fa9a2d305db945a7a625c5e563c38263af4de7be899e8b6d133b36edc9bcde21
+  data.tar.gz: 4b9f4a83e653c1f9c1e6ed5b1c69e558617e9537e29d13f588a7f1c67c7d253a28b59281f81e6831f3a7c3ab5e14915946557655950842f434545f8e0a5b4f2a

data/README.md

@@ -10,6 +10,7 @@ Create `Compoundfile` or `.gitcompound` manifest:
 
 ```ruby
   name :base_component
+  maintainer 'Your Name <your.email@example.com>'
 
   component :vendor_1 do
     version '~>1.1'
@@ -107,15 +108,22 @@ and name constraints
 
 1.  Use `name` method to specify **name** of manifest or component that this manifest is included in.
 
-2.  Add dependency to required **component** using `component` method.
+2.  Use `maintainer` method to specify maintainer of component. This can take more arguments (separated
+    by comma), for example:
 
-    This method takes two parameters -- name of component (as symbol) and implicit or explicit block.
+    ```ruby
+    maintaner 'First maintaner', 'Second maintaner'
+    ```
+
+3.  Add dependency to required **component** using `component` method.
+
+    This method takes two arguments -- name of component (as symbol) and implicit or explicit block.
 
     Beware that `GitCompound` checks name constraints, so if you rely on component
     with name `:component_1`, and this component has `Compoundfile` inside that declares 
     it's name as something else than `:component_1` -- `GitCompound` will raise exception.
 
-3.  Components can use following **version strategies**:
+4.  Components can use following **version strategies**:
 
     *   `version` -- Rubygems-like **version** strategy
         
@@ -134,18 +142,18 @@ and name constraints
         This will prevent going into detached state. If SHA does not point to any HEAD of existing branch,
         component destination repository will be left in detached state.
 
-4.  Provide path to **source** repository using `source` method of manifest domain specific language.
+5.  Provide path to **source** repository using `source` method of manifest domain specific language.
 
     It will be used as source to clone repository into destination directory.
 
-    This can take `:shallow` parameter. When `:shallow` is set, shallow clone will be 
+    This can take `:shallow` argument. When `:shallow` is set, shallow clone will be
     performed (`--branch #{ref} --depth 1`):
 
     ```ruby
     component :bootstrap do
       version '~>3.3.5'
       source 'git@github.com:twbs/bootstrap', :shallow
-      destination '/vendor/bootstrap
+      destination '/vendor/bootstrap'
     end
     ```
 
@@ -156,7 +164,7 @@ and name constraints
     Use it with caution !
 
 
-5.  Use `destination` method to specify **destination** path where component will be cloned into.
+6.  Use `destination` method to specify **destination** path where component will be cloned into.
 
     This should be relative path in most cases.
 
@@ -175,7 +183,7 @@ and name constraints
     Ceraintly components that are libraries should not use it at all. If component is project --
     it can take benefit from using absolute paths in component destination.
 
-6.  Running tasks
+7.  Running tasks
 
     It is possible to use `task` method to define new **task**. `task` method takes 2 or 3 arguments.
     First one is task name (symbol). Second one is optional task type that define how, and 
@@ -202,8 +210,8 @@ and name constraints
         ```ruby
         task :print_component_name, :each do |dir, component|
           puts "Current component name: #{component.name}"
-          puts "Current component source: #{component.origin}
-          puts "Current component destination: #{component.destination_path}
+          puts "Current component source: #{component.origin}"
+          puts "Current component destination: #{component.destination_path}"
 
           puts "Component directory: #{dir}"
         end
@@ -281,7 +289,7 @@ and name constraints
     *   replaced (remove & clone) -- if component exists but doesn't match origin remote
 
     When invoking update process via `gitcompound update` command, versions specified in manifest file
-    will be use.
+    will be used.
 
 ## Roadmap
 

data/lib/git_compound/component/version/gem_version.rb

@@ -37,7 +37,7 @@ module GitCompound
         end
 
         def to_s
-          "gem version: #{@requirement}"
+          "version: #{@requirement}"
         end
       end
     end

data/lib/git_compound/dsl/manifest_dsl.rb

@@ -14,6 +14,10 @@ module GitCompound
         @manifest.name = component_name.to_sym
       end
 
+      def maintainer(*component_maintainer)
+        @manifest.maintainer = component_maintainer
+      end
+
       def component(name, &block)
         @manifest.components.store(name.to_sym, Component.new(name, @manifest, &block))
       end

data/lib/git_compound/manifest.rb

@@ -4,7 +4,7 @@ module GitCompound
   # Manifest
   #
   class Manifest < Node
-    attr_accessor :name, :components, :tasks
+    attr_accessor :name, :maintainer, :components, :tasks
 
     FILENAMES = %w(Compoundfile .gitcompound)
 
@@ -12,6 +12,7 @@ module GitCompound
       @contents   = contents
       @parent     = parent
       @name       = ''
+      @maintainer = []
       @components = {}
       @tasks      = {}
       DSL::ManifestDSL.new(self, contents) if contents

data/lib/git_compound/version.rb

@@ -1,5 +1,5 @@
 # GitCompound
 #
 module GitCompound
-  VERSION = '0.1.1'
+  VERSION = '0.1.2'
 end

data/lib/git_compound/worker/pretty_print.rb

@@ -4,14 +4,26 @@ module GitCompound
     #
     class PrettyPrint < Worker
       def visit_component(component)
-        print_component(component)
+        pretty_print(component, " `#{component.name}` component, #{component.version}")
+      end
+
+      def visit_manifest(manifest)
+        details = []
+        details << "Component: #{manifest.name}" unless manifest.name.empty?
+        details << "Maintainer: #{manifest.maintainer.join(', ')}" unless
+          manifest.maintainer.empty?
+        details << 'Dependencies:' unless manifest.components.empty?
+
+        pretty_print(manifest, *details)
       end
 
       private
 
-      def print_component(component)
-        Logger.inline '  ' * component.ancestors.count
-        Logger.info "`#{component.name}` component, #{component.version}"
+      def pretty_print(element, *messages)
+        messages.each do |message|
+          Logger.inline '    ' * element.ancestors.count
+          Logger.info message
+        end
       end
     end
   end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: git_compound
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - Grzegorz Bizon
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2015-07-31 00:00:00.000000000 Z
+date: 2015-08-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler