necktie 0.2.1 → 0.3.0
Sign up to get free protection for your applications and to get access to all the features.
- data/README.rdoc +174 -0
- data/bin/necktie +2 -1
- data/lib/necktie/files.rb +29 -0
- data/lib/necktie/rake.rb +127 -0
- data/lib/necktie/services.rb +11 -7
- data/lib/necktie.rb +4 -54
- data/necktie.gemspec +3 -3
- data/vendor/rake/CHANGES +477 -0
- data/vendor/rake/MIT-LICENSE +21 -0
- data/vendor/rake/README.rdoc +194 -0
- data/vendor/rake/Rakefile +421 -0
- data/vendor/rake/TODO +20 -0
- data/vendor/rake/bin/rake +31 -0
- data/vendor/rake/doc/command_line_usage.rdoc +102 -0
- data/vendor/rake/doc/example/Rakefile1 +38 -0
- data/vendor/rake/doc/example/Rakefile2 +35 -0
- data/vendor/rake/doc/example/a.c +6 -0
- data/vendor/rake/doc/example/b.c +6 -0
- data/vendor/rake/doc/example/main.c +11 -0
- data/vendor/rake/doc/glossary.rdoc +51 -0
- data/vendor/rake/doc/jamis.rb +591 -0
- data/vendor/rake/doc/proto_rake.rdoc +127 -0
- data/vendor/rake/doc/rake.1.gz +0 -0
- data/vendor/rake/doc/rakefile.rdoc +566 -0
- data/vendor/rake/doc/rational.rdoc +151 -0
- data/vendor/rake/doc/release_notes/rake-0.4.14.rdoc +23 -0
- data/vendor/rake/doc/release_notes/rake-0.4.15.rdoc +35 -0
- data/vendor/rake/doc/release_notes/rake-0.5.0.rdoc +53 -0
- data/vendor/rake/doc/release_notes/rake-0.5.3.rdoc +78 -0
- data/vendor/rake/doc/release_notes/rake-0.5.4.rdoc +46 -0
- data/vendor/rake/doc/release_notes/rake-0.6.0.rdoc +141 -0
- data/vendor/rake/doc/release_notes/rake-0.7.0.rdoc +119 -0
- data/vendor/rake/doc/release_notes/rake-0.7.1.rdoc +59 -0
- data/vendor/rake/doc/release_notes/rake-0.7.2.rdoc +121 -0
- data/vendor/rake/doc/release_notes/rake-0.7.3.rdoc +47 -0
- data/vendor/rake/doc/release_notes/rake-0.8.0.rdoc +114 -0
- data/vendor/rake/doc/release_notes/rake-0.8.2.rdoc +165 -0
- data/vendor/rake/doc/release_notes/rake-0.8.3.rdoc +112 -0
- data/vendor/rake/doc/release_notes/rake-0.8.4.rdoc +147 -0
- data/vendor/rake/doc/release_notes/rake-0.8.5.rdoc +53 -0
- data/vendor/rake/doc/release_notes/rake-0.8.6.rdoc +55 -0
- data/vendor/rake/doc/release_notes/rake-0.8.7.rdoc +55 -0
- data/vendor/rake/install.rb +88 -0
- data/vendor/rake/lib/rake/alt_system.rb +108 -0
- data/vendor/rake/lib/rake/application.rb +579 -0
- data/vendor/rake/lib/rake/classic_namespace.rb +9 -0
- data/vendor/rake/lib/rake/clean.rb +35 -0
- data/vendor/rake/lib/rake/cloneable.rb +25 -0
- data/vendor/rake/lib/rake/contrib/compositepublisher.rb +24 -0
- data/vendor/rake/lib/rake/contrib/ftptools.rb +153 -0
- data/vendor/rake/lib/rake/contrib/publisher.rb +75 -0
- data/vendor/rake/lib/rake/contrib/rubyforgepublisher.rb +18 -0
- data/vendor/rake/lib/rake/contrib/sshpublisher.rb +47 -0
- data/vendor/rake/lib/rake/contrib/sys.rb +209 -0
- data/vendor/rake/lib/rake/default_loader.rb +10 -0
- data/vendor/rake/lib/rake/dsl.rb +136 -0
- data/vendor/rake/lib/rake/early_time.rb +18 -0
- data/vendor/rake/lib/rake/environment.rb +40 -0
- data/vendor/rake/lib/rake/ext/module.rb +60 -0
- data/vendor/rake/lib/rake/ext/string.rb +165 -0
- data/vendor/rake/lib/rake/ext/time.rb +14 -0
- data/vendor/rake/lib/rake/file_creation_task.rb +24 -0
- data/vendor/rake/lib/rake/file_list.rb +395 -0
- data/vendor/rake/lib/rake/file_task.rb +47 -0
- data/vendor/rake/lib/rake/file_utils.rb +108 -0
- data/vendor/rake/lib/rake/gempackagetask.rb +97 -0
- data/vendor/rake/lib/rake/invocation_chain.rb +51 -0
- data/vendor/rake/lib/rake/invocation_exception_mixin.rb +16 -0
- data/vendor/rake/lib/rake/lib/project.rake +24 -0
- data/vendor/rake/lib/rake/loaders/makefile.rb +44 -0
- data/vendor/rake/lib/rake/multi_task.rb +16 -0
- data/vendor/rake/lib/rake/name_space.rb +25 -0
- data/vendor/rake/lib/rake/packagetask.rb +184 -0
- data/vendor/rake/lib/rake/psuedo_status.rb +24 -0
- data/vendor/rake/lib/rake/rake_file_utils.rb +133 -0
- data/vendor/rake/lib/rake/rake_module.rb +25 -0
- data/vendor/rake/lib/rake/rake_test_loader.rb +15 -0
- data/vendor/rake/lib/rake/rdoctask.rb +209 -0
- data/vendor/rake/lib/rake/ruby182_test_unit_fix.rb +25 -0
- data/vendor/rake/lib/rake/rule_recursion_overflow_error.rb +20 -0
- data/vendor/rake/lib/rake/runtest.rb +23 -0
- data/vendor/rake/lib/rake/task.rb +318 -0
- data/vendor/rake/lib/rake/task_argument_error.rb +7 -0
- data/vendor/rake/lib/rake/task_arguments.rb +78 -0
- data/vendor/rake/lib/rake/task_manager.rb +328 -0
- data/vendor/rake/lib/rake/tasklib.rb +24 -0
- data/vendor/rake/lib/rake/testtask.rb +175 -0
- data/vendor/rake/lib/rake/win32.rb +55 -0
- data/vendor/rake/lib/rake.rb +72 -0
- data/vendor/rake/rake.blurb +19 -0
- data/vendor/rake/rake.gemspec +214 -0
- data/vendor/rake/rakelib/extra.rake +8 -0
- data/vendor/rake/rakelib/publish.rake +22 -0
- data/vendor/rake/rakelib/rbx.rake +82 -0
- data/vendor/rake/rakelib/ruby19.rake +88 -0
- data/vendor/rake/rakelib/tags.rake +18 -0
- data/vendor/rake/test/capture_stdout.rb +26 -0
- data/vendor/rake/test/check_expansion.rb +5 -0
- data/vendor/rake/test/check_no_expansion.rb +5 -0
- data/vendor/rake/test/contrib/test_sys.rb +47 -0
- data/vendor/rake/test/data/chains/Rakefile +15 -0
- data/vendor/rake/test/data/comments/Rakefile +18 -0
- data/vendor/rake/test/data/default/Rakefile +19 -0
- data/vendor/rake/test/data/dryrun/Rakefile +22 -0
- data/vendor/rake/test/data/file_creation_task/Rakefile +33 -0
- data/vendor/rake/test/data/imports/Rakefile +19 -0
- data/vendor/rake/test/data/imports/deps.mf +1 -0
- data/vendor/rake/test/data/multidesc/Rakefile +17 -0
- data/vendor/rake/test/data/namespace/Rakefile +66 -0
- data/vendor/rake/test/data/nosearch/dummy +1 -0
- data/vendor/rake/test/data/rakelib/test1.rb +5 -0
- data/vendor/rake/test/data/rakelib/test2.rake +3 -0
- data/vendor/rake/test/data/rbext/rakefile.rb +3 -0
- data/vendor/rake/test/data/sample.mf +14 -0
- data/vendor/rake/test/data/statusreturn/Rakefile +8 -0
- data/vendor/rake/test/data/sys/sys1.rake +3 -0
- data/vendor/rake/test/data/unittest/Rakefile +1 -0
- data/vendor/rake/test/data/unittest/subdir/README +0 -0
- data/vendor/rake/test/data/verbose/Rakefile +34 -0
- data/vendor/rake/test/filecreation.rb +32 -0
- data/vendor/rake/test/functional/functional_test.rb +15 -0
- data/vendor/rake/test/functional/session_based_tests.rb +442 -0
- data/vendor/rake/test/in_environment.rb +32 -0
- data/vendor/rake/test/lib/application_test.rb +769 -0
- data/vendor/rake/test/lib/clean_test.rb +15 -0
- data/vendor/rake/test/lib/definitions_test.rb +85 -0
- data/vendor/rake/test/lib/dsl_test.rb +41 -0
- data/vendor/rake/test/lib/earlytime_test.rb +35 -0
- data/vendor/rake/test/lib/environment_test.rb +18 -0
- data/vendor/rake/test/lib/extension_test.rb +63 -0
- data/vendor/rake/test/lib/file_creation_task_test.rb +62 -0
- data/vendor/rake/test/lib/file_task_test.rb +143 -0
- data/vendor/rake/test/lib/filelist_test.rb +623 -0
- data/vendor/rake/test/lib/fileutils_test.rb +251 -0
- data/vendor/rake/test/lib/ftp_test.rb +59 -0
- data/vendor/rake/test/lib/invocation_chain_test.rb +81 -0
- data/vendor/rake/test/lib/makefile_loader_test.rb +26 -0
- data/vendor/rake/test/lib/multitask_test.rb +53 -0
- data/vendor/rake/test/lib/namespace_test.rb +55 -0
- data/vendor/rake/test/lib/package_task_test.rb +118 -0
- data/vendor/rake/test/lib/pathmap_test.rb +210 -0
- data/vendor/rake/test/lib/pseudo_status_test.rb +26 -0
- data/vendor/rake/test/lib/rake_test.rb +41 -0
- data/vendor/rake/test/lib/rdoc_task_test.rb +88 -0
- data/vendor/rake/test/lib/require_test.rb +35 -0
- data/vendor/rake/test/lib/rules_test.rb +349 -0
- data/vendor/rake/test/lib/task_arguments_test.rb +89 -0
- data/vendor/rake/test/lib/task_manager_test.rb +173 -0
- data/vendor/rake/test/lib/task_test.rb +376 -0
- data/vendor/rake/test/lib/tasklib_test.rb +12 -0
- data/vendor/rake/test/lib/test_task_test.rb +77 -0
- data/vendor/rake/test/lib/testtask_test.rb +49 -0
- data/vendor/rake/test/lib/top_level_functions_test.rb +86 -0
- data/vendor/rake/test/lib/win32_test.rb +72 -0
- data/vendor/rake/test/rake_test_setup.rb +24 -0
- data/vendor/rake/test/reqfile.rb +3 -0
- data/vendor/rake/test/reqfile2.rb +3 -0
- data/vendor/rake/test/reqfile3.rake +3 -0
- data/vendor/rake/test/shellcommand.rb +3 -0
- data/vendor/rake/test/test_helper.rb +13 -0
- metadata +212 -56
- /data/{rush → vendor/rush}/README.rdoc +0 -0
- /data/{rush → vendor/rush}/Rakefile +0 -0
- /data/{rush → vendor/rush}/VERSION +0 -0
- /data/{rush → vendor/rush}/bin/rush +0 -0
- /data/{rush → vendor/rush}/bin/rushd +0 -0
- /data/{rush → vendor/rush}/lib/rush/access.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/array_ext.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/box.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/commands.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/config.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/dir.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/embeddable_shell.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/entry.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/exceptions.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/file.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/find_by.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/fixnum_ext.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/head_tail.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/local.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/process.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/process_set.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/remote.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/search_results.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/server.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/shell.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/ssh_tunnel.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush/string_ext.rb +0 -0
- /data/{rush → vendor/rush}/lib/rush.rb +0 -0
- /data/{rush → vendor/rush}/rush.gemspec +0 -0
- /data/{rush → vendor/rush}/spec/access_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/array_ext_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/base.rb +0 -0
- /data/{rush → vendor/rush}/spec/box_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/commands_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/config_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/dir_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/embeddable_shell_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/entry_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/file_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/find_by_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/fixnum_ext_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/local_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/process_set_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/process_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/remote_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/rush_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/search_results_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/shell_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/ssh_tunnel_spec.rb +0 -0
- /data/{rush → vendor/rush}/spec/string_ext_spec.rb +0 -0
- /data/{session → vendor/session}/lib/session-2.4.0.rb +0 -0
- /data/{session → vendor/session}/lib/session.rb +0 -0
- /data/{session → vendor/session}/test/session.rb +0 -0
@@ -0,0 +1,59 @@
|
|
1
|
+
= Rake 0.7.1 Released
|
2
|
+
|
3
|
+
Version 0.7.1 supplies a bug fix and a few minor enhancements.
|
4
|
+
|
5
|
+
== Changes
|
6
|
+
|
7
|
+
=== Bug Fixes in 0.7.1
|
8
|
+
|
9
|
+
* Changes in the exception reported for the FileUtils.ln caused
|
10
|
+
safe_ln to fail with a NotImplementedError. Rake 0.7.1 will now
|
11
|
+
catch that error or any StandardError and properly fall back to
|
12
|
+
using +cp+.
|
13
|
+
|
14
|
+
=== New Features in 0.7.1
|
15
|
+
|
16
|
+
* You can filter the results of the --task option by supplying an
|
17
|
+
optional regular expression. This allows the user to easily find a
|
18
|
+
particular task name in a long list of possible names.
|
19
|
+
|
20
|
+
* Transforming procs in a rule may now return a list of prerequisites.
|
21
|
+
This allows more flexible rule formation.
|
22
|
+
|
23
|
+
* FileList and String now support a +pathmap+ melthod that makes the
|
24
|
+
transforming paths a bit easier. See the API docs for +pathmap+ for
|
25
|
+
details.
|
26
|
+
|
27
|
+
* The -f option without a value will disable the search for a
|
28
|
+
Rakefile. This allows the Rakefile to be defined entirely in a
|
29
|
+
library (and loaded with the -r option). The current working
|
30
|
+
directory is not changed when this is done.
|
31
|
+
|
32
|
+
== What is Rake
|
33
|
+
|
34
|
+
Rake is a build tool similar to the make program in many ways. But
|
35
|
+
instead of cryptic make recipes, Rake uses standard Ruby code to
|
36
|
+
declare tasks and dependencies. You have the full power of a modern
|
37
|
+
scripting language built right into your build tool.
|
38
|
+
|
39
|
+
== Availability
|
40
|
+
|
41
|
+
The easiest way to get and install rake is via RubyGems ...
|
42
|
+
|
43
|
+
gem install rake (you may need root/admin privileges)
|
44
|
+
|
45
|
+
Otherwise, you can get it from the more traditional places:
|
46
|
+
|
47
|
+
Home Page:: http://rake.rubyforge.org/
|
48
|
+
Download:: http://rubyforge.org/project/showfiles.php?group_id=50
|
49
|
+
|
50
|
+
== Thanks
|
51
|
+
|
52
|
+
As usual, it was input from users that drove a alot of these changes.
|
53
|
+
The following people either contributed patches, made suggestions or
|
54
|
+
made otherwise helpful comments. Thanks to ...
|
55
|
+
|
56
|
+
* James Britt and Assaph Mehr for reporting and helping to debug the
|
57
|
+
safe_ln issue.
|
58
|
+
|
59
|
+
-- Jim Weirich
|
@@ -0,0 +1,121 @@
|
|
1
|
+
= Rake 0.7.2 Released
|
2
|
+
|
3
|
+
Version 0.7.2 supplies a bug fix and a few minor enhancements. In
|
4
|
+
particular, the new version fixes an incompatibility with the soon to
|
5
|
+
be released Ruby 1.8.6. We strongly recommend upgrading to Rake 0.7.2
|
6
|
+
in order to be compatible with the new version of Ruby.
|
7
|
+
|
8
|
+
== Changes
|
9
|
+
|
10
|
+
=== Bug Fixes in 0.7.2
|
11
|
+
|
12
|
+
There are quite a number of bug fixes in the new 0.7.2 version of
|
13
|
+
Rake:
|
14
|
+
|
15
|
+
* Removed dependency on internal fu_xxx functions from FileUtils.
|
16
|
+
|
17
|
+
* Error messages are now send to stderr rather than stdout (from
|
18
|
+
Payton Quackenbush).
|
19
|
+
|
20
|
+
* Better error handling on invalid command line arguments (from Payton
|
21
|
+
Quackenbush).
|
22
|
+
|
23
|
+
* Fixed some bugs where the application object was going to the global
|
24
|
+
appliation instead of using its own data.
|
25
|
+
|
26
|
+
* Fixed the method name leak from FileUtils (bug found by Glenn
|
27
|
+
Vanderburg).
|
28
|
+
|
29
|
+
* Added test for noop, bad_option and verbose flags to sh command.
|
30
|
+
|
31
|
+
* Added a description to the gem task in GemPackageTask.
|
32
|
+
|
33
|
+
* Fixed a bug when rules have multiple prerequisites (patch by Joel
|
34
|
+
VanderWerf)
|
35
|
+
|
36
|
+
* Added the handful of RakeFileUtils to the private method as well.
|
37
|
+
|
38
|
+
=== New Features in 0.7.2
|
39
|
+
|
40
|
+
The following new features are available in Rake version 0.7.2:
|
41
|
+
|
42
|
+
* Added square and curly bracket patterns to FileList#include (Tilman
|
43
|
+
Sauerbeck).
|
44
|
+
|
45
|
+
* FileLists can now pass a block to FileList#exclude to exclude files
|
46
|
+
based on calculated values.
|
47
|
+
|
48
|
+
* Added plain filename support to rule dependents (suggested by Nobu
|
49
|
+
Nakada).
|
50
|
+
|
51
|
+
* Added pathmap support to rule dependents. In other words, if a
|
52
|
+
pathmap format (beginning with a '%') is given as a Rake rule
|
53
|
+
dependent, then the name of the depend will be the name of the
|
54
|
+
target with the pathmap format applied.
|
55
|
+
|
56
|
+
* Added a 'tasks' method to a namespace to get a list of tasks
|
57
|
+
associated with the namespace.
|
58
|
+
|
59
|
+
* Added tar_command and zip_command options to the Package task.
|
60
|
+
|
61
|
+
* The clean task will no longer delete 'core' if it is a directory.
|
62
|
+
|
63
|
+
=== Internal Rake Improvements
|
64
|
+
|
65
|
+
The following changes will are mainly internal improvements and
|
66
|
+
refactorings and have little effect on the end user. But they may be
|
67
|
+
of interest to the general public.
|
68
|
+
|
69
|
+
* Added rcov task and updated unit testing for better code coverage.
|
70
|
+
|
71
|
+
* Added a 'shame' task to the Rakefile.
|
72
|
+
|
73
|
+
* Added rake_extension to handle detection of extension collisions.
|
74
|
+
|
75
|
+
* Added a protected 'require "rubygems"' to test/test_application to
|
76
|
+
unbreak cruisecontrol.rb.
|
77
|
+
|
78
|
+
* Removed rake_dup. Now we just simply rescue a bad dup.
|
79
|
+
|
80
|
+
* Refactored the FileList reject logic to remove duplication.
|
81
|
+
|
82
|
+
* Removed if __FILE__ at the end of the rake.rb file.
|
83
|
+
|
84
|
+
== What is Rake
|
85
|
+
|
86
|
+
Rake is a build tool similar to the make program in many ways. But
|
87
|
+
instead of cryptic make recipes, Rake uses standard Ruby code to
|
88
|
+
declare tasks and dependencies. You have the full power of a modern
|
89
|
+
scripting language built right into your build tool.
|
90
|
+
|
91
|
+
== Availability
|
92
|
+
|
93
|
+
The easiest way to get and install rake is via RubyGems ...
|
94
|
+
|
95
|
+
gem install rake (you may need root/admin privileges)
|
96
|
+
|
97
|
+
Otherwise, you can get it from the more traditional places:
|
98
|
+
|
99
|
+
Home Page:: http://rake.rubyforge.org/
|
100
|
+
Download:: http://rubyforge.org/project/showfiles.php?group_id=50
|
101
|
+
|
102
|
+
== Thanks
|
103
|
+
|
104
|
+
As usual, it was input from users that drove a alot of these changes.
|
105
|
+
The following people either contributed patches, made suggestions or
|
106
|
+
made otherwise helpful comments. Thanks to ...
|
107
|
+
|
108
|
+
* Payton Quackenbush -- For several error handling improvements.
|
109
|
+
|
110
|
+
* Glenn Vanderburg -- For finding and fixing the method name leak from
|
111
|
+
FileUtils.
|
112
|
+
|
113
|
+
* Joel VanderWerf -- for finding and fixing a bug in the handling of
|
114
|
+
multiple prerequisites.
|
115
|
+
|
116
|
+
* Tilman Sauerbeck -- For some enhancing FileList to support more
|
117
|
+
advanced file globbing.
|
118
|
+
|
119
|
+
* Nobu Nakada -- For suggesting plain file name support to rule dependents.
|
120
|
+
|
121
|
+
-- Jim Weirich
|
@@ -0,0 +1,47 @@
|
|
1
|
+
= Rake 0.7.3 Released
|
2
|
+
|
3
|
+
Rake version 0.7.3 is a minor release that includes some refactoring to better
|
4
|
+
support custom Rake applications.
|
5
|
+
|
6
|
+
== Changes
|
7
|
+
|
8
|
+
=== New Features in Version 0.7.3
|
9
|
+
|
10
|
+
* Added the +init+ and +top_level+ methods to make the creation of custom Rake applications a bit easier. E.g.
|
11
|
+
|
12
|
+
gem 'rake', ">= 0.7.3"
|
13
|
+
require 'rake'
|
14
|
+
|
15
|
+
Rake.application.init('myrake')
|
16
|
+
|
17
|
+
task :default do
|
18
|
+
something_interesting
|
19
|
+
end
|
20
|
+
|
21
|
+
Rake.application.top_level
|
22
|
+
|
23
|
+
== What is Rake
|
24
|
+
|
25
|
+
Rake is a build tool similar to the make program in many ways. But instead of
|
26
|
+
cryptic make recipes, Rake uses standard Ruby code to declare tasks and
|
27
|
+
dependencies. You have the full power of a modern scripting language built
|
28
|
+
right into your build tool.
|
29
|
+
|
30
|
+
== Availability
|
31
|
+
|
32
|
+
The easiest way to get and install rake is via RubyGems ...
|
33
|
+
|
34
|
+
gem install rake (you may need root/admin privileges)
|
35
|
+
|
36
|
+
Otherwise, you can get it from the more traditional places:
|
37
|
+
|
38
|
+
Home Page:: http://rake.rubyforge.org/
|
39
|
+
Download:: http://rubyforge.org/project/showfiles.php?group_id=50
|
40
|
+
|
41
|
+
== Thanks
|
42
|
+
|
43
|
+
As usual, it was input from users that drove a alot of these changes. The
|
44
|
+
following people either contributed patches, made suggestions or made
|
45
|
+
otherwise helpful comments. Thanks to ...
|
46
|
+
|
47
|
+
-- Jim Weirich
|
@@ -0,0 +1,114 @@
|
|
1
|
+
= Rake 0.8.0/0.8.1 Released
|
2
|
+
|
3
|
+
Rake version 0.8.0 is a new release of rake that includes serveral new
|
4
|
+
features.
|
5
|
+
|
6
|
+
== Changes
|
7
|
+
|
8
|
+
=== New Features in Version 0.8.0
|
9
|
+
|
10
|
+
* Tasks can now receive command line parameters. See the examples
|
11
|
+
below for more details.
|
12
|
+
|
13
|
+
* Comments are limited to 80 columns on output, but full comments can
|
14
|
+
be seen by using the -D parameter. (feature suggested by Jamis
|
15
|
+
Buck).
|
16
|
+
|
17
|
+
* Explicit exit(n) calls will now set the exit status to n. (patch
|
18
|
+
provided by Stephen Touset).
|
19
|
+
|
20
|
+
* Rake is now compatible with Ruby 1.9.
|
21
|
+
|
22
|
+
Version 0.8.1 is a minor update that includes additional Ruby 1.9
|
23
|
+
compatibility fixes.
|
24
|
+
|
25
|
+
== What is Rake
|
26
|
+
|
27
|
+
Rake is a build tool similar to the make program in many ways. But
|
28
|
+
instead of cryptic make recipes, Rake uses standard Ruby code to
|
29
|
+
declare tasks and dependencies. You have the full power of a modern
|
30
|
+
scripting language built right into your build tool.
|
31
|
+
|
32
|
+
== Availability
|
33
|
+
|
34
|
+
The easiest way to get and install rake is via RubyGems ...
|
35
|
+
|
36
|
+
gem install rake (you may need root/admin privileges)
|
37
|
+
|
38
|
+
Otherwise, you can get it from the more traditional places:
|
39
|
+
|
40
|
+
Home Page:: http://rake.rubyforge.org/
|
41
|
+
Download:: http://rubyforge.org/project/showfiles.php?group_id=50
|
42
|
+
|
43
|
+
== Task Argument Examples
|
44
|
+
|
45
|
+
Prior to version 0.8.0, rake was only able to handle command line
|
46
|
+
arguments of the form NAME=VALUE that were passed into Rake via the
|
47
|
+
ENV hash. Many folks had asked for some kind of simple command line
|
48
|
+
arguments, perhaps using "--" to separate regular task names from
|
49
|
+
argument values on the command line. The problem is that there was no
|
50
|
+
easy way to associate positional arguments on the command line with
|
51
|
+
different tasks. Suppose both tasks :a and :b expect a command line
|
52
|
+
argument: does the first value go with :a? What if :b is run first?
|
53
|
+
Should it then get the first command line argument.
|
54
|
+
|
55
|
+
Rake 0.8.0 solves this problem by explicitly passing values directly
|
56
|
+
to the tasks that need them. For example, if I had a release task
|
57
|
+
that required a version number, I could say:
|
58
|
+
|
59
|
+
rake release[0.8.0]
|
60
|
+
|
61
|
+
And the string "0.8.0" will be passed to the :release task. Multiple
|
62
|
+
arguments can be passed by separating them with a comma, for example:
|
63
|
+
|
64
|
+
rake name[john,doe]
|
65
|
+
|
66
|
+
Just a few words of caution. The rake task name and its arguments
|
67
|
+
need to be a single command line argument to rake. This generally
|
68
|
+
means no spaces. If spaces are needed, then the entire rake +
|
69
|
+
argument string should be quoted. Something like this:
|
70
|
+
|
71
|
+
rake "name[billy bob, smith]"
|
72
|
+
|
73
|
+
(Quoting rules vary between operating systems and shells, so make sure
|
74
|
+
you consult the proper docs for your OS/shell).
|
75
|
+
|
76
|
+
=== Tasks that Expect Parameters
|
77
|
+
|
78
|
+
Parameters are only given to tasks that are setup to expect them. In
|
79
|
+
order to handle named parameters, the task declaration syntax for
|
80
|
+
tasks has been extended slightly.
|
81
|
+
|
82
|
+
For example, a task that needs a first name and last name might be
|
83
|
+
declared as:
|
84
|
+
|
85
|
+
task :name, :first_name, :last_name
|
86
|
+
|
87
|
+
The first argument is still the name of the task (:name in this case).
|
88
|
+
The next to argumements are the names of the parameters expected by
|
89
|
+
:name (:first_name and :last_name in the example).
|
90
|
+
|
91
|
+
To access the values of the paramters, the block defining the task
|
92
|
+
behaviour can now accept a second parameter:
|
93
|
+
|
94
|
+
task :name, :first_name, :last_name do |t, args|
|
95
|
+
puts "First name is #{args.first_name}"
|
96
|
+
puts "Last name is #{args.last_name}"
|
97
|
+
end
|
98
|
+
|
99
|
+
The first argument of the block "t" is always bound to the current
|
100
|
+
task object. The second argument "args" is an open-struct like object
|
101
|
+
that allows access to the task arguments. Extra command line
|
102
|
+
arguments to a task are ignored. Missing command line arguments are
|
103
|
+
given the nil value.
|
104
|
+
|
105
|
+
== Thanks
|
106
|
+
|
107
|
+
As usual, it was input from users that drove a alot of these changes. The
|
108
|
+
following people either contributed patches, made suggestions or made
|
109
|
+
otherwise helpful comments. Thanks to ...
|
110
|
+
|
111
|
+
* Jamis Buck (for comment formatting suggestions)
|
112
|
+
* Stephen Touset (for exit status patch).
|
113
|
+
|
114
|
+
-- Jim Weirich
|
@@ -0,0 +1,165 @@
|
|
1
|
+
= Rake 0.8.2 Released
|
2
|
+
|
3
|
+
Rake version 0.8.2 is a new release of rake that includes a number of
|
4
|
+
new features and numerous bug fixes.
|
5
|
+
|
6
|
+
== Changes
|
7
|
+
|
8
|
+
=== New Features in Version 0.8.2
|
9
|
+
|
10
|
+
* Switched from getoptlong to optparse (patches supplied by Edwin
|
11
|
+
Pratomo).
|
12
|
+
|
13
|
+
* The -T option will now attempt to dynamically sense the size of the
|
14
|
+
terminal. The -T output will only self-truncate if the output is a
|
15
|
+
tty. However, if RAKE_COLUMNS is explicitly set, it will be honored
|
16
|
+
in any case. (Patch provided by Gavin Stark).
|
17
|
+
|
18
|
+
* The following public methods have been added to rake task objects:
|
19
|
+
|
20
|
+
* task.clear -- Clear both the prerequisites and actions of the
|
21
|
+
target rake task.
|
22
|
+
* task.clear_prerequisites -- Clear all the existing prerequisites
|
23
|
+
from the target rake task.
|
24
|
+
* task.clear_actions -- Clear all the existing actions from the
|
25
|
+
target rake task.
|
26
|
+
* task.reenable -- Re-enable a task, allowing its actions to be
|
27
|
+
executed again if the task is invoked.
|
28
|
+
|
29
|
+
* Changed RDoc test task to have no default template. This makes it
|
30
|
+
easier for the tempate to pick up the template from the environment.
|
31
|
+
|
32
|
+
* Default values for task arguments can easily be specified with the
|
33
|
+
:with_defaults method. (Idea for default argument merging supplied
|
34
|
+
by (Adam Q. Salter)
|
35
|
+
|
36
|
+
=== Bug Fixes in Version 0.8.2
|
37
|
+
|
38
|
+
* Fixed bug in package task so that it will include the subdir
|
39
|
+
directory in the package for testing. (Bug found by Adam Majer)
|
40
|
+
|
41
|
+
* Fixed filename dependency order bug in test_inspect_pending and
|
42
|
+
test_to_s_pending. (Bug found by Adam Majer)
|
43
|
+
|
44
|
+
* Fixed check for file utils options to make them immune to the
|
45
|
+
symbol/string differences. (Patch supplied by Edwin Pratomo)
|
46
|
+
|
47
|
+
* Fixed bug with rules involving multiple source, where only the first
|
48
|
+
dependency of a rule has any effect (Patch supplied by Emanuel
|
49
|
+
Inderm�hle)
|
50
|
+
|
51
|
+
* FileList#clone and FileList#dup have better sematics w.r.t. taint
|
52
|
+
and freeze.
|
53
|
+
|
54
|
+
* Changed from using Mutex to Monitor. Evidently Mutex causes thread
|
55
|
+
join errors when Ruby is compiled with -disable-pthreads. (Patch
|
56
|
+
supplied by Ittay Dror)
|
57
|
+
|
58
|
+
* Fixed bug in makefile parser that had problems with extra spaces in
|
59
|
+
file task names. (Patch supplied by Ittay Dror)
|
60
|
+
|
61
|
+
== Other changes in Version 0.8.2
|
62
|
+
|
63
|
+
* Added ENV var to rake's own Rakefile to prevent OS X from including
|
64
|
+
extended attribute junk in the rake package tar file. (Bug found by
|
65
|
+
Adam Majer)
|
66
|
+
|
67
|
+
* Added a performance patch for reading large makefile dependency
|
68
|
+
files. (Patch supplied by Ittay Dror)
|
69
|
+
|
70
|
+
== What is Rake
|
71
|
+
|
72
|
+
Rake is a build tool similar to the make program in many ways. But
|
73
|
+
instead of cryptic make recipes, Rake uses standard Ruby code to
|
74
|
+
declare tasks and dependencies. You have the full power of a modern
|
75
|
+
scripting language built right into your build tool.
|
76
|
+
|
77
|
+
== Availability
|
78
|
+
|
79
|
+
The easiest way to get and install rake is via RubyGems ...
|
80
|
+
|
81
|
+
gem install rake (you may need root/admin privileges)
|
82
|
+
|
83
|
+
Otherwise, you can get it from the more traditional places:
|
84
|
+
|
85
|
+
Home Page:: http://rake.rubyforge.org/
|
86
|
+
Download:: http://rubyforge.org/project/showfiles.php?group_id=50
|
87
|
+
|
88
|
+
== Task Argument Examples
|
89
|
+
|
90
|
+
Prior to version 0.8.0, rake was only able to handle command line
|
91
|
+
arguments of the form NAME=VALUE that were passed into Rake via the
|
92
|
+
ENV hash. Many folks had asked for some kind of simple command line
|
93
|
+
arguments, perhaps using "--" to separate regular task names from
|
94
|
+
argument values on the command line. The problem is that there was no
|
95
|
+
easy way to associate positional arguments on the command line with
|
96
|
+
different tasks. Suppose both tasks :a and :b expect a command line
|
97
|
+
argument: does the first value go with :a? What if :b is run first?
|
98
|
+
Should it then get the first command line argument.
|
99
|
+
|
100
|
+
Rake 0.8.0 solves this problem by explicitly passing values directly
|
101
|
+
to the tasks that need them. For example, if I had a release task
|
102
|
+
that required a version number, I could say:
|
103
|
+
|
104
|
+
rake release[0.8.2]
|
105
|
+
|
106
|
+
And the string "0.8.2" will be passed to the :release task. Multiple
|
107
|
+
arguments can be passed by separating them with a comma, for example:
|
108
|
+
|
109
|
+
rake name[john,doe]
|
110
|
+
|
111
|
+
Just a few words of caution. The rake task name and its arguments
|
112
|
+
need to be a single command line argument to rake. This generally
|
113
|
+
means no spaces. If spaces are needed, then the entire rake +
|
114
|
+
argument string should be quoted. Something like this:
|
115
|
+
|
116
|
+
rake "name[billy bob, smith]"
|
117
|
+
|
118
|
+
(Quoting rules vary between operating systems and shells, so make sure
|
119
|
+
you consult the proper docs for your OS/shell).
|
120
|
+
|
121
|
+
=== Tasks that Expect Parameters
|
122
|
+
|
123
|
+
Parameters are only given to tasks that are setup to expect them. In
|
124
|
+
order to handle named parameters, the task declaration syntax for
|
125
|
+
tasks has been extended slightly.
|
126
|
+
|
127
|
+
For example, a task that needs a first name and last name might be
|
128
|
+
declared as:
|
129
|
+
|
130
|
+
task :name, :first_name, :last_name
|
131
|
+
|
132
|
+
The first argument is still the name of the task (:name in this case).
|
133
|
+
The next to argumements are the names of the parameters expected by
|
134
|
+
:name (:first_name and :last_name in the example).
|
135
|
+
|
136
|
+
To access the values of the paramters, the block defining the task
|
137
|
+
behaviour can now accept a second parameter:
|
138
|
+
|
139
|
+
task :name, :first_name, :last_name do |t, args|
|
140
|
+
puts "First name is #{args.first_name}"
|
141
|
+
puts "Last name is #{args.last_name}"
|
142
|
+
end
|
143
|
+
|
144
|
+
The first argument of the block "t" is always bound to the current
|
145
|
+
task object. The second argument "args" is an open-struct like object
|
146
|
+
that allows access to the task arguments. Extra command line
|
147
|
+
arguments to a task are ignored. Missing command line arguments are
|
148
|
+
given the nil value.
|
149
|
+
|
150
|
+
== Thanks
|
151
|
+
|
152
|
+
As usual, it was input from users that drove a alot of these changes. The
|
153
|
+
following people either contributed patches, made suggestions or made
|
154
|
+
otherwise helpful comments. Thanks to ...
|
155
|
+
|
156
|
+
* Edwin Pratomo
|
157
|
+
* Gavin Stark
|
158
|
+
* Adam Q. Salter
|
159
|
+
* Adam Majer
|
160
|
+
* Emanuel Inderm�hle
|
161
|
+
* Ittay Dror
|
162
|
+
* Bheeshmar Redheendran (for spending an afternoon with me debugging
|
163
|
+
windows issues)
|
164
|
+
|
165
|
+
-- Jim Weirich
|
@@ -0,0 +1,112 @@
|
|
1
|
+
= Rake 0.8.3 Released
|
2
|
+
|
3
|
+
Rake version 0.8.3 is a bug-fix release of rake.
|
4
|
+
|
5
|
+
== Changes
|
6
|
+
|
7
|
+
=== Bug Fixes in Version 0.8.3
|
8
|
+
|
9
|
+
* Enhanced the system directory detection in windows. We now check
|
10
|
+
HOMEDRIVE/HOMEPATH and USERPROFILE if APPDATA isn't found. (Patch
|
11
|
+
supplied by James Tucker). Rake no long aborts if it can't find the
|
12
|
+
directory.
|
13
|
+
|
14
|
+
* Added fix to handle ruby installations in directories with spaces in
|
15
|
+
their name.
|
16
|
+
|
17
|
+
== What is Rake
|
18
|
+
|
19
|
+
Rake is a build tool similar to the make program in many ways. But
|
20
|
+
instead of cryptic make recipes, Rake uses standard Ruby code to
|
21
|
+
declare tasks and dependencies. You have the full power of a modern
|
22
|
+
scripting language built right into your build tool.
|
23
|
+
|
24
|
+
== Availability
|
25
|
+
|
26
|
+
The easiest way to get and install rake is via RubyGems ...
|
27
|
+
|
28
|
+
gem install rake (you may need root/admin privileges)
|
29
|
+
|
30
|
+
Otherwise, you can get it from the more traditional places:
|
31
|
+
|
32
|
+
Home Page:: http://rake.rubyforge.org/
|
33
|
+
Download:: http://rubyforge.org/project/showfiles.php?group_id=50
|
34
|
+
|
35
|
+
== Task Argument Examples
|
36
|
+
|
37
|
+
Prior to version 0.8.0, rake was only able to handle command line
|
38
|
+
arguments of the form NAME=VALUE that were passed into Rake via the
|
39
|
+
ENV hash. Many folks had asked for some kind of simple command line
|
40
|
+
arguments, perhaps using "--" to separate regular task names from
|
41
|
+
argument values on the command line. The problem is that there was no
|
42
|
+
easy way to associate positional arguments on the command line with
|
43
|
+
different tasks. Suppose both tasks :a and :b expect a command line
|
44
|
+
argument: does the first value go with :a? What if :b is run first?
|
45
|
+
Should it then get the first command line argument.
|
46
|
+
|
47
|
+
Rake 0.8.0 solves this problem by explicitly passing values directly
|
48
|
+
to the tasks that need them. For example, if I had a release task
|
49
|
+
that required a version number, I could say:
|
50
|
+
|
51
|
+
rake release[0.8.3]
|
52
|
+
|
53
|
+
And the string "0.8.3" will be passed to the :release task. Multiple
|
54
|
+
arguments can be passed by separating them with a comma, for example:
|
55
|
+
|
56
|
+
rake name[john,doe]
|
57
|
+
|
58
|
+
Just a few words of caution. The rake task name and its arguments
|
59
|
+
need to be a single command line argument to rake. This generally
|
60
|
+
means no spaces. If spaces are needed, then the entire rake +
|
61
|
+
argument string should be quoted. Something like this:
|
62
|
+
|
63
|
+
rake "name[billy bob, smith]"
|
64
|
+
|
65
|
+
(Quoting rules vary between operating systems and shells, so make sure
|
66
|
+
you consult the proper docs for your OS/shell).
|
67
|
+
|
68
|
+
=== Tasks that Expect Parameters
|
69
|
+
|
70
|
+
Parameters are only given to tasks that are setup to expect them. In
|
71
|
+
order to handle named parameters, the task declaration syntax for
|
72
|
+
tasks has been extended slightly.
|
73
|
+
|
74
|
+
For example, a task that needs a first name and last name might be
|
75
|
+
declared as:
|
76
|
+
|
77
|
+
task :name, :first_name, :last_name
|
78
|
+
|
79
|
+
The first argument is still the name of the task (:name in this case).
|
80
|
+
The next to argumements are the names of the parameters expected by
|
81
|
+
:name (:first_name and :last_name in the example).
|
82
|
+
|
83
|
+
To access the values of the paramters, the block defining the task
|
84
|
+
behaviour can now accept a second parameter:
|
85
|
+
|
86
|
+
task :name, :first_name, :last_name do |t, args|
|
87
|
+
puts "First name is #{args.first_name}"
|
88
|
+
puts "Last name is #{args.last_name}"
|
89
|
+
end
|
90
|
+
|
91
|
+
The first argument of the block "t" is always bound to the current
|
92
|
+
task object. The second argument "args" is an open-struct like object
|
93
|
+
that allows access to the task arguments. Extra command line
|
94
|
+
arguments to a task are ignored. Missing command line arguments are
|
95
|
+
given the nil value.
|
96
|
+
|
97
|
+
== Thanks
|
98
|
+
|
99
|
+
As usual, it was input from users that drove a alot of these changes. The
|
100
|
+
following people either contributed patches, made suggestions or made
|
101
|
+
otherwise helpful comments. Thanks to ...
|
102
|
+
|
103
|
+
* Edwin Pratomo
|
104
|
+
* Gavin Stark
|
105
|
+
* Adam Q. Salter
|
106
|
+
* Adam Majer
|
107
|
+
* Emanuel Inderm�hle
|
108
|
+
* Ittay Dror
|
109
|
+
* Bheeshmar Redheendran (for spending an afternoon with me debugging
|
110
|
+
windows issues)
|
111
|
+
|
112
|
+
-- Jim Weirich
|