Since the flyway tasks rely on transforming the task name in order to make the appropriate call to Flyway, one can't extend from those tasks in their gradle script and provide different tasks with different configurations. It would be nice to see the tasks refactored in such a way that the flyway command is configurable.
Since the flyway tasks rely on transforming the task name in order to make the appropriate call to Flyway, one can't extend from those tasks in their gradle script and provide different tasks with different configurations. It would be nice to see the tasks refactored in such a way that the flyway command is configurable.