Skip to content

Could lib/tasks/migrate.rake be renamed to something more unique? #468

Closed
@vergenzt

Description

@vergenzt

I'm using this library in conjunction with infrastructure/outrigger, and both libraries add a file to the Ruby load path called "lib/tasks/migrate.rake".

Each library ends up calling load "lib/tasks/migrate.rake" but only the file from the gem that appears first in $LOAD_PATH ever get loaded. (In my case, annotate_models's migrate.rake file is clobbering outrigger's, so outrigger isn't working for me.)

Could the Rake file be renamed to something involving this gem's name to avoid the conflict?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions