marceloemanoel/gradle-migrations-plugin

Mybatis migrations plugin to use with Gradle

gradle-migrations-plugin's Issues

Upgrade MyBatis to version 3.2.0

MyBatis team launched a new version.

Enable migrationsDriver configuration to have more than one driver for database agnostic applications

The class CommandHelper assumes that may only be one migration driver, but for applications that are database agnostic there may be more than just one.

Enable customization through command line arguments

All tasks parameters should be configurable through command line. All command line arguments should overwrite the default parameters of the build. Parameters should have synonyms, a descriptive and a short version such as this:

$ gradle migrateNew -Pdescription="My migration description"

should be equivalent to

$ gradle migrateNew -Pd="My migration description"

Implement Script command

iBATIS Migrations provides the script command to generate a script that can migrate a schema from one version to another.

Document release 0.2

Provide documentation for plugin version 0.2

Provide information on the following topics:

• Usage
• New Tasks
• Customization

add support for the new plugin declaration mode on gradle

i'm using gradle 2.7 and my plugins are declared in the new syntax.

Looking here it explained how the new notation is presented, although it does not explain how to make plugins to work this way

Implement Version command

The version command allow to migrate the schema to any specific version of the database you like.
You simply call it, specifying the version you’d like to end up at, and the migrations system figures out
whether it has to go up or down, and which migrations it needs to run.

Enable migrations configuration with extension point

Extension points enable namespaced configuration and customization. Enable plugin configuration with an extension point. All the common properties that exist on the plugin convention should be part of the extension point.

To use the extension point one should write such code on the build script file:

migrations {
  baseDir = "migrations" 
  environment = "development"
  force = true
}

All elements on the extension point should be optional.

Enable environment customization through migrations extension point

Instead of using properties files under

baseDir/
└── environments
    ├── development.properties
    ├── production.properties
    └── test.properties

Enable these configurations to be located on the migrations extension point like this:

migrations {
  environments {
    development {
      //development properties...       
    }
    test {
     //test properties...
    }
    production {
      //production properties
    }
  }
}

And eliminates the properties files.

Error running MigrateUp when specifying a database.

development.properties
time_zone=GMT+0:00 username=adminuser send_full_script=false password=****** delimiter=; full_line_delimeter=false auto_commit=true changelog=CHANGELOG driver=com.mysql.cj.jdbc.Driver url=jdbc:mysql://localhost:3306/admin

Result ->

:migrateUp FAILED

FAILURE: Build failed with an exception.

• What went wrong:
  Execution failed for task ':migrateUp'.

  Error executing command. Cause: java.lang.ArrayIndexOutOfBoundsException