PK @=i5 5 build.propertiesversion=1.0.3
module=liquibase-${version}
maven=mavenPK
=鰓u u build.xml
any play run-test app can be calle in this place
PK n== + + commands.py# Here you can create play commands that are specific to the module
# Example below:
# ~~~~
if play_command == 'play-liquibas:hello':
try:
print "~ Hello from play-liquibas"
sys.exit(0)
except getopt.GetoptError, err:
print "~ %s" % str(err)
print "~ "
sys.exit(-1)
sys.exit(0)PK S (>zQ$ $ manifestversion=2.1.1
frameworkVersions=1.1
PK R^s=$}[ [ README.textileh1. Liquibase Module
bq. You never develop code without version control, why do you develop your database without it ?™
p. Liquibase (http://www.liquibase.org) is a simple, reliable and elegant solution for database refactoring management. It comes with main features :
* multi dabase support (SGBDR)
* structural / data changeset
* safety check (on md5sum basis)
* safety database upgrade process (cluster is liquibase friend)
* contexts execution filter (you Player know what I'm talking about)
* automation tooling provided (ant / servlet, and now PlayFramework !)
Liquibase module differs from Migrate module for the main following reason :
h3. Database changes follow application changes just the same way source code does
h2. Getting started
Bundle changelog files within your Play application (see example),
Add liquibase dependency to your Play application
pre. # Additional modules
# ~~~~~
# A module is another play! application. Add a line for each module you want
# to add to your application. Module paths are either absolutes or relative to
# the application root.
module.liquibase=${play.path}/modules/liquibase
h2. Configuration
First version configuration options are the following :
pre. liquibase.active=true/false
liquibase.changelog=changelog_path (classpath loaded)
liquibase.properties=properties_path (classpath loaded)
liquibase.contexts=ctxt1[,ctx2]
More features (hosts execution filter, underlying database changelog structure visualization...) to come
h2. Example
p.
Changeset files / properties can be jared and integrated - thus versioned - as 3rd party libs, at module / application level, just the same way jdbc drivers are.
p.
One may also handle changeset at the same level as domainmodel declaration - that's what we do at GdTeam -, within dedicated module/application, using play module dependency mechanism to create modular app.
Modules archives are still built and maintained against 3rd party repository such as nexus / archiva / artifactory, and then released agains private / public play module repository (see http://code.google.com/p/play-repo/ for more information)
PK @=i5 5 bin/build.propertiesversion=1.0.3
module=liquibase-${version}
maven=mavenPK
=鰓u u
bin/build.xml
any play run-test app can be calle in this place
PK n== + + bin/commands.py# Here you can create play commands that are specific to the module
# Example below:
# ~~~~
if play_command == 'play-liquibas:hello':
try:
print "~ Hello from play-liquibas"
sys.exit(0)
except getopt.GetoptError, err:
print "~ %s" % str(err)
print "~ "
sys.exit(-1)
sys.exit(0)PK +q=+ + bin/play.plugins350:play.modules.liquibase.LiquibasePlugin
PK R^s=$}[ [ bin/README.textileh1. Liquibase Module
bq. You never develop code without version control, why do you develop your database without it ?™
p. Liquibase (http://www.liquibase.org) is a simple, reliable and elegant solution for database refactoring management. It comes with main features :
* multi dabase support (SGBDR)
* structural / data changeset
* safety check (on md5sum basis)
* safety database upgrade process (cluster is liquibase friend)
* contexts execution filter (you Player know what I'm talking about)
* automation tooling provided (ant / servlet, and now PlayFramework !)
Liquibase module differs from Migrate module for the main following reason :
h3. Database changes follow application changes just the same way source code does
h2. Getting started
Bundle changelog files within your Play application (see example),
Add liquibase dependency to your Play application
pre. # Additional modules
# ~~~~~
# A module is another play! application. Add a line for each module you want
# to add to your application. Module paths are either absolutes or relative to
# the application root.
module.liquibase=${play.path}/modules/liquibase
h2. Configuration
First version configuration options are the following :
pre. liquibase.active=true/false
liquibase.changelog=changelog_path (classpath loaded)
liquibase.properties=properties_path (classpath loaded)
liquibase.contexts=ctxt1[,ctx2]
More features (hosts execution filter, underlying database changelog structure visualization...) to come
h2. Example
p.
Changeset files / properties can be jared and integrated - thus versioned - as 3rd party libs, at module / application level, just the same way jdbc drivers are.
p.
One may also handle changeset at the same level as domainmodel declaration - that's what we do at GdTeam -, within dedicated module/application, using play module dependency mechanism to create modular app.
Modules archives are still built and maintained against 3rd party repository such as nexus / archiva / artifactory, and then released agains private / public play module repository (see http://code.google.com/p/play-repo/ for more information)
PK (>] U U 0 bin/play/modules/liquibase/LiquibaseAction.class 2 B &play/modules/liquibase/LiquibaseAction java/lang/Enum UPDATE (Lplay/modules/liquibase/LiquibaseAction; RUN LISTLOCKS RELEASELOCKS STATUS VALIDATE CLEARCHECKSUMS ENUM$VALUES )[Lplay/modules/liquibase/LiquibaseAction; ()V Code
(Ljava/lang/String;I)V !
$
' * ,
LineNumberTable LocalVariableTable
this values +()[Lplay/modules/liquibase/LiquibaseAction;
4 6 5 java/lang/System 7 8 arraycopy *(Ljava/lang/Object;ILjava/lang/Object;II)V valueOf <(Ljava/lang/String;)Lplay/modules/liquibase/LiquibaseAction;
< 9 = 5(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Enum;
SourceFile LiquibaseAction.java Signature :Ljava/lang/Enum;@1 @ @ @ @ @
@ @
Y Y Y Y Y" # Y% &