detroit 0.3.0 → 0.4.0

data/man/detroit.1.ronn

@@ -0,0 +1,99 @@
+detroit(1) - a life-cycle build tool
+====================================
+
+## DESCRIPTION
+
+Detroit is a software production management aid. Detroit utilizes a
+life-cycle methodology to help developers prepare and release software
+in a clear, repeatable, linear fashion. While programmed in and well
+suited to Ruby projects, Detroit can utilized for any build requirements.
+
+
+## USAGE
+
+To utilize Detroit add a `Toolchain` file to your project's root directory.
+In this file add instantiation of tools, configured to your projects build
+requirements. Toolchain files can be written in YAML or Ruby.
+
+For example to generate RDoc's for a project, a tool might be defined:
+
+    rdoc:
+      tool: rdoc
+      files:
+        - lib
+        - '[A-Z]*.*'
+      main: README.md
+
+See the online [User Guide](http://wiki.rubyworks.github.com/detroit) for
+more details on creating toolchain files.
+
+Once a toolchain file is in place, the `detroit` command line tool can be used
+to invoke the tools. For example, to generate documentation:
+
+    $ detroit document
+
+This will run through all standard stations up to and including `document`.
+Since the RDoc tool we configured above defines a document job, it would be
+run in due course.
+
+
+## OPTIONS
+
+These are the available options for the `detroit` command line tool.
+
+  * `-m`, `--multitask`
+     Run work elements in parallel.
+
+  * `-S`, `--skip=SERVICE`
+     Skip a service.
+
+  * `-s`, `--system=NAME`
+     Select assembly system. Default is 'standard'.
+
+  * `-t`, `--toolchain=FILE`
+     Use specific toolchain file(s).
+
+  * `-F`, `--force`
+     Force operations.
+
+  * `--trace`
+     Run in TRACE mode.
+
+  * `--trial`
+     Run in TRIAL mode (no disk writes).
+
+  * `--verbose`
+     Provide extra output.
+
+  * `-q`, `--quiet`
+     Run silently.
+
+  * `-I=PATH`
+    Add directory to $LOAD_PATH
+
+  * `--debug`
+     Run with $DEBUG set to true.
+
+  * `--warn`
+     Run with $VERBOSE set to true.
+
+  * `--help [TOOL]`
+     Display this help message.
+
+  * `-c`, `--config=TOOL`
+     Produce a configuration template.
+
+
+## RESOURCES
+
+* [Homepage](http://rubyworks.github.com/detroit)
+* [Development](http://github.com/rubyworks/detroit)
+* [Mailing List](http://googlegroups.com/group/rubyworks-mailinglist)
+
+
+## COPYRIGHT
+
+Copyright (c) 2011 Rubyworks
+
+Detroit is distributable in accordance with the terms of the GPL v3 license.
+

metadata

@@ -1,49 +1,85 @@
 --- !ruby/object:Gem::Specification
 name: detroit
 version: !ruby/object:Gem::Version
-  version: 0.3.0
-  prerelease: 
+  version: 0.4.0
 platform: ruby
 authors:
 - Trans
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-04-02 00:00:00.000000000 Z
+date: 2014-01-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: facets
-  requirement: &19752120 !ruby/object:Gem::Requirement
-    none: false
+  requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :runtime
   prerelease: false
-  version_requirements: *19752120
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
 - !ruby/object:Gem::Dependency
-  name: pom
-  requirement: &19751560 !ruby/object:Gem::Requirement
-    none: false
+  name: indexer
+  requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :runtime
   prerelease: false
-  version_requirements: *19751560
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: qed
-  requirement: &19751040 !ruby/object:Gem::Requirement
-    none: false
+  requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
-  version_requirements: *19751040
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: detroit-yard
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: detroit-gem
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
 description: Detroit is an advanced lifecycle build system. With Detroit, build tasks
   are user defined service instances tied to stops along a track. Whenever the detroit
   console command is run, a track is followed from beginning to designated destination.
@@ -53,65 +89,68 @@ executables:
 - detroit
 extensions: []
 extra_rdoc_files:
-- HISTORY.rdoc
-- README.rdoc
-- COPYING.rdoc
+- LICENSE.txt
 - EXAMPLE.md
+- README.md
+- HISTORY.md
 files:
-- .ruby
+- .index
 - bin/detroit
-- lib/detroit/application.rb
 - lib/detroit/assembly.rb
-- lib/detroit/assembly_system.rb
-- lib/detroit/config.rb
-- lib/detroit/control.rb
+- lib/detroit/basic_tool.rb
+- lib/detroit/basic_utils.rb
+- lib/detroit/core_ext/facets.rb
+- lib/detroit/core_ext/filetest.rb
+- lib/detroit/core_ext/shell_extensions.rb
+- lib/detroit/core_ext/to_actual_filename.rb
+- lib/detroit/core_ext/to_console.rb
+- lib/detroit/core_ext/to_list.rb
+- lib/detroit/core_ext/to_yamlfrag.rb
+- lib/detroit/core_ext/unfold_paragraphs.rb
 - lib/detroit/core_ext.rb
-- lib/detroit/custom.rb
-- lib/detroit/dsl.rb
-- lib/detroit/service.rb
-- lib/detroit/standard_assembly.rb
-- lib/detroit/tool/core_ext/facets.rb
-- lib/detroit/tool/core_ext/filetest.rb
-- lib/detroit/tool/core_ext/shell_extensions.rb
-- lib/detroit/tool/core_ext/to_actual_filename.rb
-- lib/detroit/tool/core_ext/to_console.rb
-- lib/detroit/tool/core_ext/to_list.rb
-- lib/detroit/tool/core_ext/to_yamlfrag.rb
-- lib/detroit/tool/core_ext/unfold_paragraphs.rb
-- lib/detroit/tool/core_ext.rb
-- lib/detroit/tool/email_utils.rb
-- lib/detroit/tool/project_utils.rb
-- lib/detroit/tool/shell_utils.rb
-- lib/detroit/tool.rb
+- lib/detroit/email_utils.rb
+- lib/detroit/exec.rb
+- lib/detroit/project.rb
+- lib/detroit/ruby_utils.rb
+- lib/detroit/shell_utils.rb
+- lib/detroit/toolchain/cli.rb
+- lib/detroit/toolchain/config.rb
+- lib/detroit/toolchain/runner.rb
+- lib/detroit/toolchain/script.rb
+- lib/detroit/toolchain/worker.rb
+- lib/detroit/toolchain.rb
 - lib/detroit.rb
 - lib/detroit.yml
-- HISTORY.rdoc
-- README.rdoc
-- COPYING.rdoc
+- man/detroit.1
+- man/detroit.1.html
+- man/detroit.1.ronn
 - EXAMPLE.md
+- README.md
+- HISTORY.md
+- LICENSE.txt
 homepage: http://rubyworks.github.com/detroit
 licenses:
-- GPL3
+- GPL-3.0
+metadata: {}
 post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.11
+rubygems_version: 2.0.3
 signing_key: 
-specification_version: 3
+specification_version: 4
 summary: Software Production Mangement
 test_files: []
+has_rdoc: 

data/.ruby

@@ -1,44 +0,0 @@
----
-source:
-- PROFILE
-- meta
-authors:
-- name: Trans
-  email: transfire@gmail.com
-copyrights:
-- holder: Thomas Sawyer
-  year: '2007'
-  license: GPL3
-requirements:
-- name: facets
-- name: pom
-- name: qed
-  groups:
-  - test
-  development: true
-dependencies: []
-alternatives: []
-conflicts: []
-repositories:
-- uri: http://github.com/proutils/detroit.git
-  scm: git
-  name: upstream
-resources:
-  home: http://rubyworks.github.com/detroit
-  code: http://github.com/rubyworks/detroit
-  mail: http://groups.google.com/rubyworks-mailinglist
-extra: {}
-load_path:
-- lib
-revision: 0
-created: '2007-10-10'
-summary: Software Production Mangement
-title: Detroit
-version: 0.3.0
-name: detroit
-suite: detroit
-description: Detroit is an advanced lifecycle build system. With Detroit, build tasks
-  are user defined service instances tied to stops along a track. Whenever the detroit
-  console command is run, a track is followed from beginning to designated destination.
-organization: rubyworks
-date: '2012-04-01'

data/README.rdoc

@@ -1,132 +0,0 @@
-= Detroit
-
-{Homepage}[http://rubyworks.github.com/detroit] /
-{Development}[http://github.com/rubyworks/detroit] /
-{Mailing List}[http://googlegroups.com/group/rubyworks-mailinglist]
-
-
-== DESCRIPTION
-
-Detroit is a software production management aid for Ruby developers.
-Detroit utilizes a life-cycle methodology to help developers prepare and
-release Ruby software in a clear, repeatable, linear fashion.
-
-
-== HOW IT WORKS
-
-Detroit defines development processions which consist of a set of named 
-production _lines_, or _tracks_, each with a series of named _stations_,
-or _stops_. Developers attach work elements to stations by configuring
-service instances in a project's Schedule or *.schedule files. Schedules
-are written in either YAML or a Ruby DSL.
-
-For example, a RubyForge service can be defined:
-
-  rubyforge:
-    service: Rubyforge
-    sitemap:
-      site: <%= name %>
-    active: true
-
-As this example demonstrates, service configurations can draw on project
-metadata via ERB embedded tags. Detroit gathers this information using
-{.ruby}[http://dotruby.github.com/dotruby], but the data source can be
-easily customized to meet the needs of different projects.
-
-With service configuration and metadata in place, using Detroit is simply
-a matter of passing a line name and stop to the +detroit+ command line
-tool. For example,
-
-  $ detroit main:document
-
-The track name and its stop are separated by a colon. This command
-would run every stop on the +main+ track, in order, until it completes
-the +document+ stop. Since +main+ is the default track, we can acheive
-the same effect without specifying it.
-
-  $ detroit document
-
-The use of tracks may seem constrictive to users of tools like Rake, but
-there is a benefit to this approach. It helps ensure a project is 
-always up-to-date and in-sync --that no necessary steps are missed.
-Detroit includes three tracks out of the box. The most significant of
-which is +main+ which entails a route with ordred stops:
-
-  prepare     # prepare services and ensure requirements
-  generate    # code generation
-  compile     # compile source code
-  test        # run tests and/or specifications
-  analyze     # run code analysis
-  document    # generate documentation
-  package     # create packages
-  verify      # post package verification (eg. integration tests)
-  install     # install package locally
-  publish     # publish website/documentation
-  release     # release packages
-  deploy      # deply system to servers
-  promote     # tell the world about you awesome work
-
-All tracks also have a maintainence subtrack which consits of three stops:
-
-  reset       # mark build files as out-of-date
-  clean       # remove minor build files
-  purge       # remove all build files
-
-Where reset marks generated files out-of-date, clean removes temporary
-products and purge removes all generated prodcuts.
-
-In additon to +main+, Detroit includes +site+ and +attn+ tracks which are used
-to generate and publish a project's website, and make project announcements
-respectively. They are simply useful subsets of the +main+ track.
-
-Please see http://rubyworks.github.com/detroit for more details on how to
-use Detroit, including the creation of custom tracks, stops and service plugins.
-Also try the <tt>--help</tt> option to see the detroit command's help
-information.
-
-
-== INSTALLATION
-
-Detroit can, of course, be installed via RubyGems:
-
-  $ gem install detroit
-
-We no longer recommend it, but Detroit can also be installed the
-old-fashion way by downloading the .tar.gz package and using
-Ruby Setup (See http://setup.rubyforge.org).
-
-  $ tar -xvzf detroit-1.0.0.tar.gz
-  $ cd detroit-1.0.0
-  $ sudo setup.rb
-
-Ruby Setup is stand-alone version of the original setup.rb script.
-
-
-== ISSUES
-
-All in all, Detroit works well. There are some rough edges with regards
-to the built-in service plugins, so from time to time you might run into
-an odd error. Ususally it just means a service confirguraiton needs 
-adjustment.
-
-Please note, Windows support has not been considered at all. While I do
-not see any specific reason it should not work, there may well be issues
-I have not considered since I do not use Windows. If you are Windows user
-and give Detroit a try please let us know of any issues you encounter.
-
-
-== HISTORY
-
-Detroit is actaully the offspring of Reap v10, and was called Syckle for 
-a number of years as it matured. It represents many years of design considerations
-(and reconsiderations) that evolved Reap from its simple Rake extension origins,
-which pre-dated Hoe, to the life-cycle system it is today.
-
-
-== COPYRIGHT & LICENSE
-
-(GPL v3 License)
-
-Copyright (c) 2007 Thomas Sawyer
-
-See COPYING.rdoc and GPL3.txt for details.