|
3 | 3 |
|
4 | 4 | 1) Clone adapter http://github.com/rails-sqlserver/2000-2005-adapter. |
5 | 5 | 2) The master branch is the one under development for rails 3. |
6 | | - 3) Set the ARSQLSERVER_SOURCE environment variable with the path of this repo. |
7 | 6 |
|
8 | | -= Arel Testing Setup |
9 | | - |
10 | | - 1) Clone our fork of Arel. http://github.com/rails-sqlserver/arel |
11 | | - 2) Switch to remote tracking branch "sqlserver" |
12 | | - 3) Set the AREL environment variable with path of this repo. |
13 | | - |
14 | | -= Rails |
| 7 | += Rails & Arel Testing Setup |
15 | 8 |
|
16 | 9 | 1) Clone rails. |
17 | 10 | 2) Creat a local topic branch, maybe something like sqlserver_3.0.0.beta |
18 | 11 | 3) Apply the following diff, till we push this upstream. http://gist.github.com/443568 |
19 | 12 | 4) Set the RAILS_SOURCE environment variable with the path of this repo. |
| 13 | + 5) It is optional, but you can set an AREL environment variable to the official |
| 14 | + git fork of arel at rails/arel. As of now there is no need to do this as our |
| 15 | + Gemfile will source this and we currently host our own compiler in this project. |
20 | 16 |
|
21 | 17 | = Testing Last Steps And Notes |
22 | 18 |
|
23 | 19 | So bundler manages the dependencies now and if you have set the correct environment |
24 | | -variables then all dependency paths for development should be resolved. It is now best to |
25 | | -run "bundle install" first from your Arel, then to the adapter repo. Now you should be able |
26 | | -to run "bundle exec rake spec:sqlserver" in Arel to run tests. Since we put bundler as |
27 | | -a development dependency in the adapter, all you need to do is run "rake test". |
| 20 | +variables then all dependency paths for development should be resolved. Please use |
| 21 | +the latest 1.0.0 beta of Bundler. Since we put bundler as a development dependency in |
| 22 | +the adapter, all you need to do is run "rake test" after bundling. |
28 | 23 |
|
29 | 24 | Remember you have to set an environment variable for the DSN of the adapter, see the ODBC |
30 | 25 | connection information for details. Lastly, it is typically good practice to do your work |
|
0 commit comments