Menu

Tree [r7] /
 History

HTTPS access


File Date Author Commit
 examples 2009-05-20 neeleshs [r7]
 lib 2008-11-04 neeleshs [r3] Jars
 src 2009-05-20 neeleshs [r7]
 test 2009-05-20 neeleshs [r7]
 .classpath 2009-02-06 neeleshs [r4] Added sub-revisions (example: 20.1, 20.1.1 etc)...
 .project 2008-10-24 neeleshs [r1] First cut. Simple SQL based migration
 README 2008-11-04 neeleshs [r2] Fixes to incorporate Spring, README
 build.properties 2008-10-24 neeleshs [r1] First cut. Simple SQL based migration
 build.xml 2008-11-04 neeleshs [r2] Fixes to incorporate Spring, README
 examples.xml 2008-10-24 neeleshs [r1] First cut. Simple SQL based migration

Read Me

* Put evolver-0.1.jar and evolver.properties in to classpath

* Change evolver.properties to suit your database

* Create a package somewhere in your source tree to hold migration files

* Create either Java or SQL migration files. The SQL files should start with a number. The Java files should have the name in the following format
Revision<No>.java where <No> is the revision number. Java and SQL files can live together, as long as the revision numbers don't clash
  
* To run the migrations, run the class com.motn.evole.Evolver, with migrations, evolve-0.1.jar and evolver.properties under classpath

* See examples.xml if you need an ant target for evolve