Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using (deprecated) init goal in Maven takes wrong baseline version #892

Closed
agattung opened this issue Nov 28, 2014 · 0 comments
Closed

Using (deprecated) init goal in Maven takes wrong baseline version #892

agattung opened this issue Nov 28, 2014 · 0 comments

Comments

@agattung
Copy link

@agattung agattung commented Nov 28, 2014

After upgrading to Flyway 3.1:
When executing the "init" goal with Maven plugin, Flyway takes wrong baseline version.

Log says: "Schema baselined with version: 1"
config says: 0.1.0.000

As a consequence my delta scripts were not executed, since they start with "0.".

After changing "init" to "baseline" everything is fine.

@axelfontaine axelfontaine added this to the Flyway 3.2 milestone Nov 28, 2014
@axelfontaine axelfontaine changed the title Flyway 3.1: Using (deprecated) init goal in Maven takes wrong init/baselined version Using (deprecated) init goal in Maven takes wrong init/baselined version Nov 28, 2014
@axelfontaine axelfontaine changed the title Using (deprecated) init goal in Maven takes wrong init/baselined version Using (deprecated) init goal in Maven takes wrong baseline version Nov 28, 2014
axelfontaine added a commit to flyway/flywaydb.org that referenced this issue Nov 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.