roundhouse 0.5.0.242 → 0.5.0.248

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification 
 name: roundhouse
 version: !ruby/object:Gem::Version 
-  hash: 387
+  hash: 407
   prerelease: false
   segments: 
   - 0
   - 5
   - 0
-  - 242
-  version: 0.5.0.242
+  - 248
+  version: 0.5.0.248
 platform: ruby
 authors: 
 - Rob "FerventCoder" Reynolds
@@ -19,7 +19,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-07-15 00:00:00 -05:00
+date: 2010-07-23 00:00:00 -05:00
 default_executable: 
 dependencies: []
 
@@ -32,16 +32,7 @@ extensions: []
 extra_rdoc_files: []
 
 files: 
-- lib/docs/buildCustomization/package.post.step
-- lib/docs/GettingStarted.docx
-- lib/docs/logo/roundhouse.ico
-- lib/docs/logo/RoundhousE_Logo.jpg
-- lib/docs/logo/RoundhousE_Logo_NoBackground.gif
-- lib/docs/RoundhousE.dot
-- lib/docs/RoundhousEPresentation.pptx
-- lib/LEGAL/LICENSE
-- lib/LEGAL/NOTICE
-- lib/ReadMe.txt
+- lib/rh.exe
 - bin/rh
 - bin/rh.exe
 has_rdoc: true

data/lib/LEGAL/LICENSE

@@ -1,174 +0,0 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.

data/lib/LEGAL/NOTICE

@@ -1,9 +0,0 @@
-=========================================================================
-==  Example NOTICE file for use with the Apache License, Version 2.0,  ==
-==  in this case for the Apache httpd-2.0 distribution.                ==
-=========================================================================
-
-UppercuTs
-Copyright 2007-2008 The Apache Software Foundation.
-
-

data/lib/ReadMe.txt

@@ -1,118 +0,0 @@
-Project RoundhousE - Database Change Management done right
-=======
-![RoundhousE](http://github.com/ferventcoder/roundhouse/raw/master/docs/logo/RoundhousE_Logo.jpg "RoundhousE - Professional Database Management.")  
-
-# LICENSE
-Apache 2.0 - see docs\legal (just LEGAL in the zip folder)
-
-# IMPORTANT
-NOTE: If you are looking at the source - please run build.bat before opening the solution. It creates the SolutionVersion.cs file that is necessary for a successful build.
-
-# INFO
-## Overview
-RoundhousE is an automated database deployment (change management) system that allows you to use your current idioms and gain much more. Currently it only supports Microsoft SQL Server, but there are future plans for other databases. 
-
-It seeks to solve both maintenance concerns and ease of deployment. We follow some of the same idioms as other database management systems (SQL scripts), but we are different in that we think about future maintenance concerns. We want to always apply certain scripts (anything stateless like functions, views, stored procedures, and permissions), so we don�t have to throw everything into our change scripts. This seeks to solves future source control concerns. How sweet is it when you can version the database according to your current source control version? 
-
-## Getting started with RoundhousE
-### Downloads
- You can download RoundhousE from [http://code.google.com/p/roundhouse/downloads/list](http://code.google.com/p/roundhouse/downloads/list)  
-
- You can also obtain a copy from the build server at [http://teamcity.codebetter.com](http://teamcity.codebetter.com).  
-
-### Source
-This is the best way to get to the bleeding edge of what we are doing.  
-
-1. Clone the source down to your machine.  
-  `git clone git://github.com/chucknorris/roundhouse.git`  
-2. Type `cd roundhouse`  
-3. Type `git config core.autocrlf true` to set line endings to auto convert for this repository  
-4. Type `git status`. You should not see any files to change.
-5. Run `build.bat`. NOTE: You must have git on the path (open a regular command line and type git).
-  
-  
-# REQUIREMENTS
-* .NET Framework 3.5  
-* SQL Server 2005/2008 installed (or required DLLS in the GAC for SQL Server 2005/2008)  
-* SA access to the sql server (for creation or deletion)  
-* change access to the database (for everything else)  
-
-# DONATE
-Donations Accepted - If you enjoy using this product or it has saved you time and money in some way, please consider making a donation.  
-It helps keep to the product updated, pays for site hosting, etc. https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=9831498
-
-# RELEASE NOTES
-=0.5.0.188=  
-* RH handles nonsupported DDL transactions. RH will also stop and inform the user when DDL transactions are not supported, so user can choose to continue - see [issue 28](http://code.google.com/p/roundhouse/issues/detail?id=28) for details. (r172 - branch, r185)  
-* RH logs when errors occur in the RoundhousE.ScriptRunErrors table - see [issue 28](http://code.google.com/p/roundhouse/issues/detail?id=28) for details. (r167 - branch, r185)  
-* RH supports SQL Server 2000 - see [issue 30](http://code.google.com/p/roundhouse/issues/detail?id=30) for details. (r167 - branch, r185)  
-* RH supports Oracle - see [issue 34](http://code.google.com/p/roundhouse/issues/detail?id=34) for details. (r157 - branch, r185)  
-  
-=0.2.0.175=  
-* RH should handle when user names have apostrophes (') in them - see [issue 32](http://code.google.com/p/roundhouse/issues/detail?id=32) for details. (r175)  
-* Database names should have delimiters to allow for non standard characters - see [issue 31](http://code.google.com/p/roundhouse/issues/detail?id=31) for details. (r174)  
-* Added autowiring permissions sample. (r169)  
-* If copying to change output fails, log a warning and move on. (r156)  
-  
-=0.2.0.150=  
-* Turning off batch splitting where it is not necessary as it does affect performance. (r150)  
-* Splitting statements on GO has been enhanced to catch end of file GOs - see [issue 25](http://code.google.com/p/roundhouse/issues/detail?id=25) for details. (r149)  
-  
-=0.2.0.148=  
-* Splitting statements on GO has been enhanced - see [issue 25](http://code.google.com/p/roundhouse/issues/detail?id=25) for details. (r147)  
-  
-=0.2.0.144=  
-* Splitting statements on GO is now a two-phased approach - see [issue 25](http://code.google.com/p/roundhouse/issues/detail?id=25) for details. (r143)  
-* Trying out StructureMap (r136)  
-  
-=0.2.0.131=  
-* More fine-grained splitting by the word GO - see [issue 25](http://code.google.com/p/roundhouse/issues/detail?id=25) for details. (r130)  
-* Command timeout became more explicit so database decorators can access and manipulate the value now. (r129)  
-* RH should be able to use ADO.NET instead of SMO for SqlServer - see [issue 22](http://code.google.com/p/roundhouse/issues/detail?id=22) for details. (r125)  
-* Option not to create a database if none exists - see [issue 24](http://code.google.com/p/roundhouse/issues/detail?id=24) for details. (r123)  
-* Console should exit with an error code instead of crashing on errors - see [issue 23](http://code.google.com/p/roundhouse/issues/detail?id=23) for details. (r119)  
-  
-=0.2.0.117=  
-* Restore timeouts can now be specified (with a default timeout of 900 seconds) - see [issue 21](http://code.google.com/p/roundhouse/issues/detail?id=21) for details. (r117)  
-* Custom database create scripts are now possible - see [issue 20](http://code.google.com/p/roundhouse/issues/detail?id=20) for details. (r116)  
-* All types of migrations will split sql statements from files that have more than one statement into multiple statements and run each consecutively - see [issue 27](http://code.google.com/p/roundhouse/issues/detail?id=17) for details. (r113)  
-* Fixed issue with running roundhouse twice during MSBuild - see [issue 16](http://code.google.com/p/roundhouse/issues/detail?id=16) for details. (r112)  
-  
-=0.2.0.108=  
-* Reports version during run - see [issue 9](http://code.google.com/p/roundhouse/issues/detail?id=9) for details. (r108)  
-* Logs what type of script it is looking for and where it is looking for them - see [issue 14](http://code.google.com/p/roundhouse/issues/detail?id=14) for details. (r107)  
-* Removed double error reporting on exception. (r107)  
-* Adding getting started documentation  
-* Added a custom restore option to add additional arguments (like MOVE) to a restore - see [issue 12](http://code.google.com/p/roundhouse/issues/detail?id=12) for details. (r104)  
-* Fixed a connection string initialization issue (r103)  
-  
-=0.2.0.101=  
-* File Sorting - Fixed a sorting issue with file names to do explicit sorting. (r101)  
-* RH has an icon of the logo (r99)  
-  
-=0.2.0.97=  
-* OleDB Support - RH can now be run for advanced database connections with a connection string. (r96)  
-  - OleDB may not support creating/restoring/deleting databases.  
-  - Microsoft Access is supported through OleDB.  
-  - Other databases will need to have scripts written for their type before they would be supported.  
-   
-=0.0.0.86=  
-* Environment awareness - RH determines an environment file first that it has ".ENV." in the file name and then if it is the proper environment file based on whether the file also contains the specific environment name. For example LOCAL.0001_DoSomething.ENV.sql will run in the LOCAL environment but no where else.  
-* Runs permissions files every time regardless of changes.  
-  
-=0.0.0.85=  
-* Added synonyms for database types - see [issue 10](http://code.google.com/p/roundhouse/issues/detail?id=10) for details. (r85)  
-* Removed some of the logging - no more event logging for limited permissions running (r83)  
-  
-=0.0.0.82=  
-* The command line version (rh.exe) is merged into a single assembly with all dependencies (except Microsoft.SQL dlls) internalized. No configuration file necessary either. (r77, r82)  
-* Log from console runner is now copied into the change_drop folder. (r81)  
-* Recovery mode is now explicit. Default is full. Otherwise pass in /simple - see [issue 8](http://code.google.com/p/roundhouse/issues/detail?id=8) for details. (r78)  
-* Excluded the drop database from transactions (not that you would call /drop with /t). (r76)  
-  
-=0.0.0.74=  
-* Fixed an issue with holding connections - see [issue 7](http://code.google.com/p/roundhouse/issues/detail?id=7) for details. (r74)  
-* Added the ability to run with transactions  
-  
-# CREDITS
-UppercuT - Automated Builds (automated build in 10 minutes or less?!) [http://projectuppercut.org](http://projectuppercut.org)

data/lib/docs/buildCustomization/package.post.step

@@ -1,52 +0,0 @@
-<?xml version="1.0" encoding="utf-8" ?>
-<project name="Packager" default="go">
-  <property name="dirs.current" value="${directory::get-parent-directory(project::get-buildfile-path())}" />
-  <property name="path.to.toplevel" value=".." />
-  <property name="folder.build_scripts" value="build" overwrite="false" />
-  <property name="folder.build_scripts_custom" value="build.custom" overwrite="false" />
-  <property name="dirs.build_scripts_custom" value="${dirs.current}\${path.to.toplevel}\${folder.build_scripts_custom}" />
-  <property name="folder.code_build" value="build_output" overwrite="false" />
-  <property name="dirs.build" value="${dirs.current}\${path.to.toplevel}\${folder.code_build}" />
-  <property name="folder.code_drop" value="code_drop" overwrite="false" />
-  <property name="dirs.drop" value="${dirs.current}\${path.to.toplevel}\${folder.code_drop}" overwrite="false" />
-  <property name="folder.app.drop" value="${project.name}" overwrite="false" />
-  <property name="folder.database" value="__DATABASE_FOLDER_NAME__" overwrite="false" />
-  <property name="folder.reports" value="${project.name}.Reports" overwrite="false" />
-  <property name="folder.file_server" value="file.server" overwrite="false" />
-  <property name="folder.environment_files" value="environment.files" overwrite="false" />
-  <property name="folder.deployment" value="deployment" overwrite="false" />
-  <property name="folder.settings" value="settings" overwrite="false" />
-  <property name="folder.documentation" value="docs" overwrite="false" />
-
-
-  <target name="go" depends="package_nant_in_deploy_folder, package_roundhouse_in_deploy_folder" description="Packaging" />
-
-  <target name="package_nant_in_deploy_folder">
-    <echo message="Moving NAnt over to deployment folder" />
-    <copy todir="${dirs.drop}\${folder.deployment}\NAnt" >
-      <fileset basedir="${dirs.current}\..\lib\NAnt">
-        <exclude name="**\*.template" />
-        <include name="**/*.*" />
-      </fileset>
-    </copy>
-  </target>
-  
-  <target name="package_roundhouse_in_deploy_folder">
-    <echo message="Moving RoundhousE over to deployment folder" />
-    <copy todir="${dirs.drop}\${folder.deployment}\NAnt" >
-      <fileset basedir="${dirs.current}\..\lib\RoundhousE">
-        <include name="**/*.*" />
-      </fileset>
-    </copy>
-  </target>
-  
-  <target name="copy_roundhouse_files_to_deploy_console">
-    <echo message="Copying roundhouse assemblies to ${dirs.deployment}\Console."/>
-    <copy todir="${dirs.deployment}\Console">
-      <fileset basedir="${dirs.current}\..\lib\RoundhousE">
-        <include name="**/*.*" />
-      </fileset>
-    </copy>
-  </target>
-  
-</project>