albacore 0.6.2.rc1 → 1.0.0.rc.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: c1e2e74b02e67eb95188c0877c91bdd4fccbe430
+  data.tar.gz: 3c0c9660d7c0dfde9a5295a55d91221a4510ba97
+SHA512:
+  metadata.gz: 661046323ec3746f3dee00c77bde928889e9cbfee1b7b20b958bb35881ef08de37fd75f8653eb5ca840c051f6b808c16a9d62e6685d10cb6f4303a97801ceb9e
+  data.tar.gz: 67e05ef730f5b3fa0558ac0cdf514f71fe597807dfbc03d628c227a23491094f2b53a98ba1b963a50f36f5f34033de0e75b0fa57aff5c48e6d8e41b80451eb7e

data/.bundle/config

@@ -0,0 +1,2 @@
+---
+BUNDLE_WITHOUT: wiki

data/.gitignore

@@ -1,5 +1,24 @@
-Gemfile.lock
-tmp/
 *.swp
+*~
+.idea
+
+Gemfile.lock
+
 pkg/
-.DS_Store
+obj/
+bin/
+build/
+
+_ReSharper.*
+*.csproj.user
+*.resharper.user
+*.resharper
+*.suo
+*.cache
+~$*
+*.tmp
+*.eprj
+*.bkp
+
+/spec/support/Tools/NDepend-v2.12/NDependProLicense.xml
+Gemfile.lock

data/.rspec

@@ -0,0 +1,2 @@
+--color
+--format progress

data/.rvmrc

@@ -0,0 +1 @@
+rvm 1.9.3@albacore --create

data/.travis.yml

@@ -1,13 +1,15 @@
-language: ruby
-rvm:
-  - 1.9.3
-  - jruby
-script: "bundle exec rake spec"
-branches:
-  only:
-    - clean_slate
-#env:
-notifications:
-  email: false
-
-gemfile: Gemfile
+language: ruby
+rvm:
+  - 1.9.2
+  - 1.9.3
+  - 2.0.0
+  - jruby
+script: "bundle exec rake specs:assemblyinfo specs:albacoremodel specs:attrmethods"
+branches:
+  only:
+    - dev
+#env:
+bundler_args: --without=wiki
+notifications:
+  email: false
+gemfile: Gemfile

data/CONTRIBUTING.md

@@ -0,0 +1,87 @@
+# Contributing
+
+You can contribute to the Albacore framework in many ways.
+
+* Submit or comment on [issues list][1].
+* Discuss development on the [user group][2].
+* Ask questions at [StackOverflow][11].
+* Submit or comment on [pull requests][12].
+* Contribute to the [wiki][13], especially the tasks docs
+
+## Overview
+
+Start by [forking the repository][3]. Make your changes in the *dev* branch (or a feature branch, whichever you're most comfortable with). Make sure to add or edit tests, as necessary. Submit your pull request to the Albacore/albacore *dev* branch. You will be notified by Travis, our servant, whether your pull request passes all tests. When the code has been reviewed and merged, it will be included in the next gem.
+
+Be sure to set your [line-endings][4] correctly for your platform, *before* you start developing.
+
+## Building the Albacore Package
+
+tl;dr
+
+```bat
+cmd> git clone git://github.com/Albacore/albacore.git -b dev
+cmd> gem install bundler
+cmd> bundle
+cmd> rake install
+```
+
+The full instructions for building the Albacore package should be similar to other Github and Ruby gem projects. Fork or clone the Albacore/albacore repository and immediately use the *dev* branch.
+
+```bat
+cmd> git clone git://github.com/Albacore/albacore.git -b dev
+```
+
+You need the Bundler gem to install all of the Albacore development and runtime dependencies.
+
+```bat
+cmd> gem install bundler
+```
+
+If you are developing on the Windows platform, you will also need the [RubyInstaller Development Kit][8] (DevKit). There are complicated [manual install instructions][9], but we recommend using the [DevKit package][10] from Chocolatey. Then, you can ask Bundler to install the dependencies listed in the `Gemfile` and `albacore.gemspec`.
+
+```bat
+cmd> bundle install
+```
+
+You can build the Albacore `.gem` package using the built-in rake task.
+
+```bat
+cmd> rake build
+```
+
+And you may install that same gem on your local system
+
+```bat
+cmd> gem install --local path/to/albacore.x.y.z.gem
+```
+
+Or, you can build & install in one step
+
+```bat
+cmd> rake install
+```
+
+## Running Tests with RSpec
+
+You can get a list of the available spec categories by running `rake -T`, they start with `specs:`. The `specs:all` task will run *all* of the specs. You can colorize the spec run output on your console with RSpec `~>2.7` and [ansicon][5]. We recommend installing the [ansicon package][6] using the [Chocolatey][7] package manager.
+
+```bat
+cmd> rake specs:all
+```
+
+The NCover and NDepend specs categories require a valid license to be installed on your system or they will fail. You can ignore those failures or run the special specs category `specs:except_ncover`.
+
+
+ [1]: http://github.com/Albacore/albacore/issues 
+ [2]: http://groups.google.com/group/albacoredev
+ [3]: http://help.github.com/forking/
+ [4]: http://help.github.com/dealing-with-lineendings/
+ [5]: http://adoxa.3eeweb.com/ansicon/ 
+ [6]: http://chocolatey.org/packages/ansicon
+ [7]: http://chocolatey.org/
+ [8]: http://rubyinstaller.org/add-ons/devkit/
+ [9]: https://github.com/oneclick/rubyinstaller/wiki/Development-Kit
+ [10]: http://chocolatey.org/packages/ruby.devkit
+ [11]: http://stackoverflow.com/questions/tagged/albacore
+ [12]: https://github.com/Albacore/albacore/pulls
+ [13]: https://github.com/Albacore/albacore/wiki

data/Gemfile

@@ -1,14 +1,6 @@
-#ruby=1.9.3
-#ruby-gemset=albacore_clean_slate
-
-source "http://rubygems.org"
-
-# Windows Rubies (RubyInstaller)
-platforms :mswin, :mingw do
-  gem 'wdm' # for listening to Windows Directory Notifications
-end
-
-# needed to do development and read the version of albacore
-gem 'nokogiri', '~>1.5'
-
-gemspec
+source "http://rubygems.org"
+gemspec
+
+group :wiki do
+  gem "jekyll"
+end

data/Guardfile

@@ -1,7 +1,9 @@
 # A sample Guardfile
 # More info at https://github.com/guard/guard#readme
-guard 'rspec' do
+
+guard 'rspec', :version => 2 do
   watch(%r{^spec/.+_spec\.rb$})
   watch(%r{^lib/(.+)\.rb$})     { |m| "spec/lib/#{m[1]}_spec.rb" }
+  watch('spec/spec_helper.rb')  { "spec" }
 end
 

data/LICENSE

@@ -0,0 +1,21 @@
+# MIT License
+
+Copyright (c) 2011 Derick Bailey, Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -1,148 +1,47 @@
-# Albacore Clean Slate
-
-[![Build Status](https://secure.travis-ci.org/Albacore/albacore.png?branch=clean_slate)](http://travis-ci.org/Albacore/albacore)
-
-This branch is the next official version. It is currently being used for
-numerous builds for us and is free of known bugs. It works on RMI 1.9.3 and
-jRuby.
-
-## getting started
-
-In a command prompt, run:
-
-    @powershell -NoProfile -ExecutionPolicy unrestricted -Command "iex ((new-object net.webclient).DownloadString('http://chocolatey.org/install.ps1'))" && SET PATH=%PATH%;%systemdrive%\chocolatey\bin
-
-Then start a new powershell, cygwin or mingw32 shell. You can now install the
-Ruby framework:
-
-    cinst ruby.devkit
-
-Now, restart your shell or reload its path variable. You now have rake
-installed. Now you can install Albacore, the collection of tasktypes, tasks and
-extension points aimed to make your life as a .Net developer easier:
-
-    gem install bundler
-
-Bundler is a tool that fetches gems for you. Now, specify what ruby gems your
-build will use. Create a new file, named `Gemfile`. This file should look like
-this:
-
-    source 'http://rubygems.org'
-    gem "albacore", :git => "git://github.com/Albacore/albacore.git", :branch => 'clean_slate'
-
-Now, install albacore from this repository by running:
-
-    bundle
-
-In order to build your project, you need to create a `Rakefile`, with contents
-like these:
-
-    require 'bundler/setup'
-
-    require 'albacore'
-    require 'albacore/tasks/versionizer'
-    require 'albacore/ext/teamcity'
-
-    Albacore::Tasks::Versionizer.new :versioning
-
-    desc "Perform fast build (warn: doesn't d/l deps)"
-    build :quick_build do |b|
-      b.logging = 'detailed'
-      b.sln = 'src/MyProj.sln'
-    end
-
-    desc "Perform full build"
-    build :build => [:versioning, :restore] do |b|
-      b.sln = 'src/MyProj.sln'
-    end
-
-    directory 'build/pkg'
-
-    nugets_restore :restore do |p|
-      p.out = 'src/packages'
-      p.exe = 'buildsupport/NuGet.exe'
-    end
-
-    desc "package nugets"
-    nugets_pack :create_nugets => ['build/pkg', :versioning, :build] do |p|
-      p.files   = FileList['src/**/*.{csproj,fsproj,nuspec}'].
-        exclude('src/Fsharp.Actor/*.nuspec').
-        exclude(/Tests/).
-        exclude(/Spec/).
-        exclude(/sample/).
-        exclude(/packages/)
-      p.out     = 'build/pkg'
-      p.exe     = 'buildsupport/NuGet.exe'
-      p.version = ENV['NUGET_VERSION']
-    end
- 
-You can now run:
-
-    rake
-
-## hack guidelines
-
-Use pair-of-three: `Cmd`, `Config` and `Task`. Add Rakefile-methods in `dsl.rb`.
-You can `include CmdConfig` in your `Config` to get access to parameters, and do
-`include CrossPlatformCmd` in your `Cmd` to get correct cross-platform, logging
-and invocation of system and shell statements.
-
-Read the READMEs in the `lib/ext` and `lib/tasks` folders. Write unit-tests for
-your functionality. Try to make the execution of the command that you have
-prepared be a single line of code that does something like: `sh make_command`
-thereby delegating to `CrossPlatformCmd`. To ignore exit codes, call `shie`
-instead.
-
-Use and document `attr_accessor` in `Config` with [TomDoc](http://tomdoc.org/),
-so that docs can be automatically generated. Have sane defaults. If an option is
-true/false, have a sane default and provide a method that sets the opposite.
-Document the default. Document required properties to set. Don't set properties
-by providing single-parameter methods, because it's confusing with regards to
-reading those same properties.
-
-'Execute' the configuration as much as possible when configuring it through the
-DSL block, but don't do side-effects other than fail bad config. Remember that
-multiple interactions with the `Config` object is desired. Do side-effects when
-the task is run.
-
-How to write commands:
-
-    require 'map'
-
-    # ...
-
-    def initialize executable, *args
-      opts = Map.options(args)
-      @executable = executable  
-    end
-
-In general: look at the written code and do something similar =).
-
-Provide further blocks/lambdas/procs, passed from the `Config` to the `Task` or
-even `Cmd` if you need to decide values when the task is run. This makes it
-easier to compose tasks.
-
-I use a vague concept of 'core albacore' for tasktypes (nugets_restore,
-nugets_pack, build) and 'extensions' for things that depend on published
-symbols, and 'tasks' for things that can be instantiated (added to the Rake
-Tasks collection) in the Rakefile. Your extension probably is a 'task' or
-'extension'.
-
-Use ideomatic ruby. If you have more than 3 levels of indentation in a method,
-you're probably not being ideomatic. Can you use a higher-level language
-construct or the null-object pattern or some functional programming concept that
-makes the code easier to read, reason about and maintain? Don't mutate unless
-you have to - code that doesn't mutate much can be gotten by using the builder
-pattern (`Config` is the builder most of the time); then, a lot of the logic of
-how to construct the command-line/expression to run, can be done in the
-constructor (`Cmd#initialize`), rather than when executing it.
-
-## Links
-
- * http://guides.rubygems.org/make-your-own-gem/
- * http://postmodern.github.com/2012/05/22/rubygems-tasks.html
- * https://github.com/guard/guard-rspec
- * http://barkingiguana.com/2011/12/13/how-i-structure-rubygems/
- * http://rakeroutes.com/blog/lets-write-a-gem-part-one/
- * https://github.com/sj26/ruby-1.9.3-p0/blob/master/lib/rake/application.rb
- * https://github.com/sj26/ruby-1.9.3-p0/blob/master/lib/rake/rake_module.rb
+# Albacore 
+[![Build Status](https://secure.travis-ci.org/Albacore/albacore.png?branch=dev)](http://travis-ci.org/Albacore/albacore) [![Gem Version](https://badge.fury.io/rb/albacore.png)](http://badge.fury.io/rb/albacore) [![Dependency Status](https://gemnasium.com/Albacore/albacore.png)](https://gemnasium.com/Albacore/albacore) [![Code Climate](https://codeclimate.com/github/Albacore/albacore.png)](https://codeclimate.com/github/Albacore/albacore) [![Coverage Status](https://coveralls.io/repos/Albacore/albacore/badge.png)](https://coveralls.io/r/Albacore/albacore)
+
+Albacore is a professional quality suite of Rake tasks for building .NET or Mono based systems. It's like MSBuild or NAnt without all the stabby-bracket XML hell! The tasks are built using a test-first approach and all tests are included in the gem. If you're new to Ruby/Rake read the [quick start][2]. Or, browse the [detailed instructions][1] for each task in our wiki. 
+
+Details about goals and releases can be found at [albacorebuild.net](http://albacorebuild.net) and by following [@albacorebuild](https://twitter.com/albacorebuild).
+
+## Installation
+
+Add this line to the Gemfile where you maintain the dependencies for your build:
+
+```ruby
+gem "albacore"
+```
+
+And then execute
+
+```bat
+> bundle
+```
+    
+Or install it yourself:
+
+```bat
+> gem install albacore
+```
+
+## Usage
+
+Require the Albacore gem at the top of your rakefile and start using the custom tasks. Consult the [quick start][3] or the detailed [task instructions][1] for more information on how to use Albacore tasks in your Rake build.
+
+```ruby
+require "albacore"
+```
+
+## Supported Rubies
+
+Albacore has been tested against the following versions of Ruby for Windows and Linux. Use unsupported versions at your own risk!
+
+* MRI: `1.9.2`, `1.9.3`, `2.0.0`
+* JRuby: `HEAD`
+
+
+
+ [1]: https://github.com/Albacore/albacore/wiki
+ [2]: https://github.com/Albacore/albacore/wiki#rake-quick-start
+ [3]: https://github.com/Albacore/albacore/wiki#albacore-quick-start

data/Rakefile

@@ -1,9 +1,24 @@
-require 'rubygems/tasks'
-Gem::Tasks.new
-
-require 'rspec/core/rake_task'
-RSpec::Core::RakeTask.new(:spec) do |c|
-  c.rspec_opts = ['--color', '--format=doc']
-end
-
-task :default => :build
+require "bundler/gem_tasks"
+
+task :default => :"specs:all"
+
+namespace :specs do
+  require "rspec/core/rake_task"
+
+  desc "Run all specs"
+  RSpec::Core::RakeTask.new(:all)
+
+  # generate tasks for each *_spec.rb file in the root spec folder
+  exceptNCov = []
+  FileList["spec/*_spec.rb"].each do |fname|
+    spec = $1 if /spec\/(.+)_spec\.rb/ =~ fname
+    exceptNCov << spec unless /ncover|ndepend/ =~ spec
+    desc "Run the #{spec} spec"
+    RSpec::Core::RakeTask.new spec do |t|
+      t.pattern = "spec/#{spec}*_spec.rb"
+    end
+  end
+
+  desc "Run specs:all except :ncover, :ndepend"
+  task :except_ncover => exceptNCov
+end