Bug. Composer + Subversion repo + --no-dev flag.

[Петр Захария]

Hi, I have a problem using --no-dev flag to update my vendor folder. If defined "require-dev" config block, and I run

composer.phar update --no-dev

Composer updates packages to the version defined in "require-dev" block but not in "require" block if  version of package set to * in "require" block. 

More info.

I'm using Subversion repository with standart structure - trunk, tags, branches. If set config composer.json:

{

    "require": {

        "company/library": "*"

    },

    "require-dev": {

        "company/library": "dev-trunk"

    },

    "repositories": [

        {

            <Subversion repository definition>

        }

    ]

 }

And we run

composer.phar update --no-dev

we'll get _trunk_ version of company/library package.

If we'll delete "require-dev" block:

{

    "require": {

        "company/library": "*"

    },

    "repositories": [

        {

            <Subversion repository definition>

        }

    ]

 }

and run the same command, we'll get latest tag of the package 

In my opinion/ if we set --no-dev flag, "require-dev" config block shouldn't be used to decide wich version to checkout.