taskmapper 0.8.0 → 0.8.1

data/Gemfile

@@ -1,8 +1,8 @@
-source :rubygems
+source 'https://rubygems.org'
 
 gem 'activeresource', '~> 3.0'
 gem 'activesupport', '~> 3.0'
-gem 'hashie', "~> 1.2"
+gem 'hashie', "~> 2.0"
 
 group :test, :development  do
   gem 'rspec', '~> 2.0'

data/Gemfile.lock

@@ -1,5 +1,5 @@
 GEM
-  remote: http://rubygems.org/
+  remote: https://rubygems.org/
   specs:
     activemodel (3.2.2)
       activesupport (= 3.2.2)
@@ -13,7 +13,7 @@ GEM
     builder (3.0.0)
     diff-lcs (1.1.3)
     git (1.2.5)
-    hashie (1.2.0)
+    hashie (2.0.3)
     i18n (0.6.0)
     jeweler (1.8.3)
       bundler (~> 1.0)
@@ -45,7 +45,7 @@ PLATFORMS
 DEPENDENCIES
   activeresource (~> 3.0)
   activesupport (~> 3.0)
-  hashie (~> 1.2)
+  hashie (~> 2.0)
   jeweler (~> 1.8)
   rcov (~> 1.0)
   rspec (~> 2.0)

data/README.md

@@ -1,20 +1,20 @@
-# taskmapper
+# Taskmapper
 
-taskmapper is a Gem which eases communication with various project and ticket management systems by providing a consistent Ruby API.
+Taskmapper is a Gem which eases communication with various project and ticket management systems by providing a consistent Ruby API.
 
-taskmapper let's you "remap" a system into the consistent taskmapper API, easily. For instance the description of an issue/ticket, might be named **description** in one system, and **problem-description** somewhere else. Via taskmapper, this would always be called **description**. The taskmapper remaps makes it easy for you to integrate different kinds of ticket systems, into your own system. You don't have to take care of all the different kinds of systems, and their different APIs. taskmapper handles all this *for* you, so you can focus on making your application awesome.
+Taskmapper let's you "remap" a system into the consistent Taskmapper API, easily. For instance the description of an issue/ticket, might be named **description** in one system, and **problem-description** somewhere else. Via Taskmapper, this would always be called **description**. The Taskmapper remaps makes it easy for you to integrate different kinds of ticket systems, into your own system. You don't have to take care of all the different kinds of systems, and their different APIs. Taskmapper handles all this *for* you, so you can focus on making your application awesome.
 
 ## Installation
 
-taskmapper is a Gem, so we can easily install it by using RubyGems:
+Taskmapper is a Gem, so we can easily install it by using RubyGems:
 
     gem install taskmapper
 
-taskmapper depends on [Hashie](http://github.com/intridea/hashie), which is an amazing library which makes converting objects to hashes, and the other way around, a joy. It should be installed automatically whenever installing taskmapper.
+Taskmapper depends on [Hashie](http://github.com/intridea/hashie), which is an amazing library which makes converting objects to hashes, and the other way around, a joy. It should be installed automatically whenever installing taskmapper.
 
 ### Finding and installing a provider
 
-taskmapper by itself won't do too much. You may want to install a provider, to retrieve a list of available providers issue the following command:
+Taskmapper by itself won't do too much. You may want to install a provider, to retrieve a list of available providers issue the following command:
 
     gem search taskmapper
 
@@ -32,30 +32,30 @@ First, we instance a new class with the right set of options. In this example, w
 
 ### Grabbing a project
 
-Now that we've got out taskmapper instance, let's go ahead and grab "testproject":
+Now that we've got out Taskmapper instance, let's go ahead and grab "testproject":
 
     project = pivotal.project["testproject"]
-        #=> taskmapper::Project<#name="testproject"..>
+        #=> TaskMapper::Project<#name="testproject"..>
 
 *Project#[]* is an alias to *Project#find*:
 
     project = pivotal.project.find "testproject"
-        #=> taskmapper::Project<#name="testproject"..>
+        #=> TaskMapper::Project<#name="testproject"..>
 
 Which translates into:
 
     project = pivotal.project.find :name => "testproject"
-        #=> taskmapper::Project<#name="testproject"..>
+        #=> TaskMapper::Project<#name="testproject"..>
 
 That means you can actually look up a project by something else than the title, like the owner:
 
     project = pivotal.project.find :owner => "Sirupsen"
-        #=> taskmapper::Project<#owner="sirupsen"..>
+        #=> TaskMapper::Project<#owner="sirupsen"..>
 
 To retrieve all projects, simply pass no argument to find:
 
     project = pivotal.project.find
-        #=> [taskmapper::Project<#..>,TaskMapper::Project<#..>,..]
+        #=> [TaskMapper::Project<#..>,TaskMapper::Project<#..>,..]
 
 ### Creating a ticket
 
@@ -70,12 +70,12 @@ We create our ticket with three properties.
 Alright, let's play with the projects tickets! Here we grab the ticket with the id of 22:
 
     ticket = project.tickets(:id => 22)
-        #=> taskmapper::Ticket<#id=22..>
+        #=> TaskMapper::Ticket<#id=22..>
 
 Like with projects, we can also find tickets by other attributes, like title, priority and so on, with tickets we do not use a find method though. Also as with projects, if no argument is passed, all tickets are retrieved:
 
     tickets = project.tickets
-        #=> [taskmapper::Ticket<#..>,TaskMapper::Ticket<#..>,..]
+        #=> [TaskMapper::Ticket<#..>,TaskMapper::Ticket<#..>,..]
 
 ### Changing ticket attributes
 
@@ -109,14 +109,14 @@ However, as closing a ticket with a resolution is such a common task, the other
 
 ## Support
 
-Currently taskmapper supports the following systems:
+Currently Taskmapper supports the following systems:
 
 ### Pivotal Tracker
 
-To use Pivotal Tracker with taskmapper, install it:
+To use Pivotal Tracker with Taskmapper, install it:
     gem install taskmapper-pivotal
 
-Then simply require it, and you are good to use Pivotal Tracker with taskmapper!
+Then simply require it, and you are good to use Pivotal Tracker with Taskmapper!
 
     require 'taskmapper'
     require 'taskmapper-pivotal'
@@ -126,10 +126,10 @@ The source code is located at [taskmapper-pivotal](http://github.com/hybridgroup
 
 ### Lighthouse
 
-To use Lighthouse with taskmapper, install it:
+To use Lighthouse with Taskmapper, install it:
     gem install taskmapper-lighthouse
 
-Then simply require it, and you are all set to use Lighthouse with taskmapper!
+Then simply require it, and you are all set to use Lighthouse with Taskmapper!
 
     require 'taskmapper'
     require 'taskmapper-lighthouse'
@@ -139,10 +139,10 @@ The source code is located at [taskmapper-lighthouse](http://github.com/hybridgr
 
 ### Basecamp
 
-To use Basecamp with taskmapper, install it:
+To use Basecamp with Taskmapper, install it:
     gem install taskmapper-basecamp
 
-Once you require it, then you are ready to use Basecamp with taskmapper
+Once you require it, then you are ready to use Basecamp with Taskmapper
 
     require 'taskmapper'
     require 'taskmapper-basecamp'
@@ -152,10 +152,10 @@ The source code is located at [taskmapper-basecamp](http://github.com/hybridgrou
 
 ### Github
 
-To use Github's issue tracking with taskmapper, install it:
+To use Github Issue tracking with Taskmapper, install it:
     gem install taskmapper-github
 
-Once you require it, then you are ready to use Github and taskmapper
+Once you require it, then you are ready to use Github and Taskmapper
 
     require 'taskmapper'
     require 'taskmapper-github'
@@ -165,10 +165,10 @@ The source code is located at [taskmapper-github](http://github.com/hybridgroup/
 
 ### Unfuddle
 
-To use Unfuddle with taskmapper, install it:
+To use Unfuddle with Taskmapper, install it:
     gem install taskmapper-unfuddle
 
-Then simply require it, and you are good to use Unfuddle with taskmapper!
+Then simply require it, and you are good to use Unfuddle with Taskmapper!
 
     require 'taskmapper'
     require 'taskmapper-unfuddle'
@@ -176,12 +176,12 @@ Then simply require it, and you are good to use Unfuddle with taskmapper!
 
 The source code is located at [taskmapper-unfuddle](http://github.com/hybridgroup/taskmapper-unfuddle)
 
-### Kanban Pad
+### Kanbanpad
 
-To use Kanban Pad with taskmapper, install it:
+To use Kanbanpad with taskmapper, install it:
     gem install taskmapper-kanbanpad
 
-Once you require it, you can connect to Kanban Pad using taskmapper!
+Once you require it, you can connect to Kanbanpad using Taskmapper!
 
     require 'taskmapper'
     require 'taskmapper-kanbanpad'
@@ -191,10 +191,10 @@ The source code is located at [taskmapper-kanbanpad](https://github.com/hybridgr
 
 ### Redmine
 
-To use Redmine with taskmapper, install it:
+To use Redmine with Taskmapper, install it:
     gem install taskmapper-redmine
 
-Just require it, and you are ready to use Redmine with taskmapper!
+Just require it, and you are ready to use Redmine with Taskmapper!
 
     require 'taskmapper'
     require 'taskmapper-redmine'
@@ -204,10 +204,10 @@ The source code is located at [taskmapper-redmine](http://github.com/hybridgroup
 
 ### Trac
 
-To use Trac with taskmapper, install it:
+To use Trac with Taskmapper, install it:
     gem install taskmapper-trac
 
-Require it, and you are happening to call Trac with taskmapper!
+Require it, and you are happening to call Trac with Taskmapper!
 
     require 'taskmapper'
     require 'taskmapper-trac'
@@ -215,25 +215,12 @@ Require it, and you are happening to call Trac with taskmapper!
 
 The source code is located at [taskmapper-trac](http://github.com/hybridgroup/taskmapper-trac)
 
-### Codaset
-
-To use Codaset with taskmapper, install it:
-    gem install taskmapper-codaset
-
-Require and you have connected to Codaset with taskmapper!
-
-    require 'taskmapper'
-    require 'taskmapper-codaset'
-    codaset = taskmapper.new(:codaset, {:username => "foo", :password => "bar", :client_id => "your_client_id", :client_secret => "your_client_secret"})
-
-The source code is located at [taskmapper-codaset](http://github.com/hybridgroup/taskmapper-codaset)
-
 ### Bugzilla
 
-To use Bugzilla with taskmapper, install it:
+To use Bugzilla with Taskmapper, install it:
     gem install taskmapper-bugzilla
 
-Require and you can talk to Bugzilla with taskmapper!
+Require and you can talk to Bugzilla with Taskmapper!
 
     require 'taskmapper'
     require 'taskmapper-bugzilla'
@@ -249,18 +236,18 @@ Creating a provider consists of three steps:
 * Implement whatever is needed to connect to your desired backend
 * Release it to RubyGems
 
-### Create the taskmapper provider
+### Create the Taskmapper provider
 Thanks to a simple generator, it is easy to get started with a new provider. Run this from the command line:
     tm generate myprovider
 
 This will generate a new skeleton provider called taskmapper-myprovider in the current directory. Create a repo from that directory, and you can start implementing your provider.
 
-Almost all APIs are different. And so are their Ruby providers. taskmapper attempts to create an universal API for ticket and project management systems, and thus, we need to map the functionality to the taskmapper API. This is the providers job. The provider is the glue between taskmapper, and the ticket management system's API.
+Almost all APIs are different. And so are their Ruby providers. Taskmapper attempts to create an universal API for ticket and project management systems, and thus, we need to map the functionality to the Taskmapper API. This is the providers job. The provider is the glue between Taskmapper, and the task management system's API.
 Usually, your provider would rely on another library for the raw HTTP interaction. For instance, [taskmapper-lighthouse](http://github.com/hybridgroup/taskmapper-lighthouse) relies on ActiveResource in order to interact with the Lighthouse API. Look at it like this:
 
-**taskmapper** -> **Provider** -> *(Ruby library)* -> **Site's API**
+**Taskmapper** -> **Provider** -> *(Ruby library)* -> **Site's API**
 
-Provider being the *glue* between the site's API and taskmapper. The Ruby library is "optional" (though highly recommended as mentioned), therefore it is in parantheses.
+Provider being the *glue* between the site's API and Taskmapper. The Ruby library is "optional" (though highly recommended as mentioned), therefore it is in parantheses.
 
 An example of a provider could be [taskmapper-lighthouse](http://github.com/hybridgroup/taskmapper-lighthouse), an example of a Ruby library could be ActiveResource.
 
@@ -293,4 +280,4 @@ They should be presented with a nice list of all available providers.
 
 ## Copyright
 
-Copyright (c) 2010 [The Hybrid Group](http://hybridgroup.com). See LICENSE for details.
+Copyright (c) 2010-2012 [The Hybrid Group](http://hybridgroup.com). See LICENSE for details.

data/VERSION

@@ -1 +1 @@
-0.8.0
+0.8.1

data/taskmapper.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = "taskmapper"
-  s.version = "0.8.0"
+  s.version = "0.8.1"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["kiafaldorius", "Sirupsen", "deadprogrammer"]
-  s.date = "2012-05-09"
+  s.date = "2013-04-01"
   s.description = "TaskMapper provides a universal API to ticket tracking and project management systems."
   s.email = "info@hybridgroup.com"
   s.executables = ["tm"]
@@ -82,7 +82,7 @@ Gem::Specification.new do |s|
   ]
   s.homepage = "http://ticketrb.com"
   s.require_paths = ["lib"]
-  s.rubygems_version = "1.8.15"
+  s.rubygems_version = "1.8.25"
   s.summary = "TaskMapper provides a universal API to ticket tracking and project management systems."
 
   if s.respond_to? :specification_version then
@@ -91,7 +91,7 @@ Gem::Specification.new do |s|
     if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
       s.add_runtime_dependency(%q<activeresource>, ["~> 3.0"])
       s.add_runtime_dependency(%q<activesupport>, ["~> 3.0"])
-      s.add_runtime_dependency(%q<hashie>, ["~> 1.2"])
+      s.add_runtime_dependency(%q<hashie>, ["~> 2.0"])
       s.add_development_dependency(%q<rspec>, ["~> 2.0"])
       s.add_development_dependency(%q<jeweler>, ["~> 1.8"])
       s.add_development_dependency(%q<simplecov>, ["~> 0.5"])
@@ -99,7 +99,7 @@ Gem::Specification.new do |s|
     else
       s.add_dependency(%q<activeresource>, ["~> 3.0"])
       s.add_dependency(%q<activesupport>, ["~> 3.0"])
-      s.add_dependency(%q<hashie>, ["~> 1.2"])
+      s.add_dependency(%q<hashie>, ["~> 2.0"])
       s.add_dependency(%q<rspec>, ["~> 2.0"])
       s.add_dependency(%q<jeweler>, ["~> 1.8"])
       s.add_dependency(%q<simplecov>, ["~> 0.5"])
@@ -108,7 +108,7 @@ Gem::Specification.new do |s|
   else
     s.add_dependency(%q<activeresource>, ["~> 3.0"])
     s.add_dependency(%q<activesupport>, ["~> 3.0"])
-    s.add_dependency(%q<hashie>, ["~> 1.2"])
+    s.add_dependency(%q<hashie>, ["~> 2.0"])
     s.add_dependency(%q<rspec>, ["~> 2.0"])
     s.add_dependency(%q<jeweler>, ["~> 1.8"])
     s.add_dependency(%q<simplecov>, ["~> 0.5"])

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: taskmapper
 version: !ruby/object:Gem::Version
-  version: 0.8.0
+  version: 0.8.1
   prerelease: 
 platform: ruby
 authors:
@@ -11,11 +11,11 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-05-09 00:00:00.000000000Z
+date: 2013-04-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activeresource
-  requirement: &88047140 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -23,10 +23,15 @@ dependencies:
         version: '3.0'
   type: :runtime
   prerelease: false
-  version_requirements: *88047140
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '3.0'
 - !ruby/object:Gem::Dependency
   name: activesupport
-  requirement: &88046840 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -34,21 +39,31 @@ dependencies:
         version: '3.0'
   type: :runtime
   prerelease: false
-  version_requirements: *88046840
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '3.0'
 - !ruby/object:Gem::Dependency
   name: hashie
-  requirement: &88046560 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
-        version: '1.2'
+        version: '2.0'
   type: :runtime
   prerelease: false
-  version_requirements: *88046560
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '2.0'
 - !ruby/object:Gem::Dependency
   name: rspec
-  requirement: &88046230 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -56,10 +71,15 @@ dependencies:
         version: '2.0'
   type: :development
   prerelease: false
-  version_requirements: *88046230
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '2.0'
 - !ruby/object:Gem::Dependency
   name: jeweler
-  requirement: &88045960 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -67,10 +87,15 @@ dependencies:
         version: '1.8'
   type: :development
   prerelease: false
-  version_requirements: *88045960
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '1.8'
 - !ruby/object:Gem::Dependency
   name: simplecov
-  requirement: &88045650 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -78,10 +103,15 @@ dependencies:
         version: '0.5'
   type: :development
   prerelease: false
-  version_requirements: *88045650
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '0.5'
 - !ruby/object:Gem::Dependency
   name: rcov
-  requirement: &88045310 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -89,7 +119,12 @@ dependencies:
         version: '1.0'
   type: :development
   prerelease: false
-  version_requirements: *88045310
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '1.0'
 description: TaskMapper provides a universal API to ticket tracking and project management
   systems.
 email: info@hybridgroup.com
@@ -173,6 +208,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
   - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
+      segments:
+      - 0
+      hash: 2657740509767190220
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
@@ -181,7 +219,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.15
+rubygems_version: 1.8.25
 signing_key: 
 specification_version: 3
 summary: TaskMapper provides a universal API to ticket tracking and project management