Project

General

Profile

Actions

Defect #10838

closed

Rails 3 Can't rollback plugins migrations

Added by John Yani almost 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

The following command

rake redmine:plugins:migrate VERSION=0

run my plugins migrations again instead of rolling back.

Actions #1

Updated by John Yani almost 12 years ago

Oh, it should've been in lower case "version". Documentation should be edited then before release.

Actions #2

Updated by Jean-Philippe Lang almost 12 years ago

  • Status changed from New to Closed
  • Resolution set to Invalid

Your command is invalid with trunk@9646. When you specify a version, you have to specify the plugin name too:

$rake redmine:plugins:migrate VERSION=0
The VERSION argument requires a plugin NAME.

If you want to migrate/rollback a plugin to a specific version (eg. 0), you have to give its name:

rake redmine:plugins:migrate NAME=sample_plugin VERSION=0

And it works with VERSION=0 or version=0.

Actions #3

Updated by John Yani almost 12 years ago

Jean-Philippe Lang wrote:

If you want to migrate/rollback a plugin to a specific version (eg. 0), you have to give its name:

rake redmine:plugins:migrate NAME=sample_plugin VERSION=0

Your example is also invalid. It has to be

rake redmine:plugins:migrate name=sample_plugin version=0

It's in lower case. As you can see here:

http://www.redmine.org/projects/redmine/repository/entry/trunk/lib/tasks/redmine.rake#L56

So the prompt should be

The version argument requires a plugin name.

Actions #4

Updated by Jean-Philippe Lang almost 12 years ago

  • Assignee set to Jean-Philippe Lang
  • Resolution changed from Invalid to Fixed

OK, yet another difference between ruby and ruby/win32...
Fixed in r9647.

Actions

Also available in: Atom PDF