Issue 515 in flyway: Current 2.x versions <flyway:info> requires locations while older versions didn't.

[fly...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-AntTasks OpSys-All

New issue 515 by bjoern.k...@gmail.com: Current 2.x versions <flyway:info>
requires locations while older versions didn't.
http://code.google.com/p/flyway/issues/detail?id=515

We've upgraded our 1.7 flyway to 2.2.
When running <flyway:info> now (it used to be <flyway:status> but I changed
it to the new tag) it claims it cannot find "db/migrate".

Which is correct, because we use a different folder structure than the
default location "db/migrate".

The problem here is that we defined the locations for each <flyway:migrate>
task seperately and never for the <flyway:info> tasks.

I have fixed the problem now by adding the <locations> tag or setting the
global locations property. But my main question is:

Why does <flyway:info> need to know the location of the migration files at
all when all it does is print the schemaversion table content without ever
touching the migrations directories?


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[fly...@googlecode.com]

Comment #1 on issue 515 by bjoern.k...@gmail.com: Current 2.x versions

<flyway:info> requires locations while older versions didn't.
http://code.google.com/p/flyway/issues/detail?id=515

oops. Didn't notice you are using github now. Will repost there.

[fly...@googlecode.com]

Updates:
Status: Migrated

Comment #2 on issue 515 by axel.fontai...@gmail.com: Current 2.x

versions <flyway:info> requires locations while older versions didn't.
http://code.google.com/p/flyway/issues/detail?id=515

(No comment was entered for this change.)