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

mvn db-migrator:drop should not throw error if database does not exist #1221

Closed
konstantsin123 opened this issue Aug 4, 2022 · 2 comments
Closed

Comments

@konstantsin123
Copy link

Now: mvn db-migrator:create throw an error if database already present.

Expected: mvn db-migrator:create throw a warning if database already present.

@ipolevoy ipolevoy self-assigned this Aug 4, 2022
@ipolevoy ipolevoy changed the title mvn db-migrator:create should not throw error if database already present mvn db-migrator:drop should not throw error if database does not exist Aug 4, 2022
@ipolevoy
Copy link
Member

ipolevoy commented Aug 4, 2022

Changing this to:

Now:

mvn db-migrator:drop 

throws an error if a database does not exist. If the Drop mojo just prints a warning, it will be easier to use it in scripts.

@ipolevoy ipolevoy closed this as completed Aug 4, 2022
ipolevoy added a commit that referenced this issue Aug 4, 2022
#1221 - mvn db-migrator:drop should not throw error  if database does…
@ipolevoy
Copy link
Member

ipolevoy commented Aug 4, 2022

deployed to Sonatype with version: 3.0-SNAPSHOT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants