Skip to content

Composer installer doesn't detect changing deploystrategy #134

Open
@ihor-sviziev

Description

@ihor-sviziev

After changing deployment strategy from "copy" to "symlink" (and back) and execute composer update - Output:

Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Writing lock file
Generating autoload files

For now I found hack: remove my module from composer.json that exec composer update and that back module to composer.json. Only after that I have changed deploy strategy (but only for this module).

I think installer should detect changing strategy.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions