Add support for "autoload-dev"

[alsar]

Composer has a possibility to define autoload roles for development purposes.
https://getcomposer.org/doc/04-schema.md#autoload-dev

The main purpose of this is for test classes. These classes are only included in the autoloader in development.

Currently there is no support for this inside the composer plugin.

The usecase inside the plugin for this feature could be, that there can be different rules for autosugestion.
For regular source files the autosugestion would exclude the "autoload-dev" classes, but inside test classes full autosugestion (including autoload-dev) would be available.

What do you think?

[gossi]

I think this sounds like a great addition. When Robert and me thought about the buildpath management we had these test sources in mind. That's why you can add includes and excludes manually to the build-path management.

One quick question, because I can't find it in the docs. Is this triggered via composer install --(no-)dev? And will it autoload only the dev sources from the root package or recursively from all installed packages?

[alsar]

It's autoload-dev is triggered on composer install (you don't need to specify --dev).
I think it will load only dev sources from the root package, but I'm not 100% sure. I can check it later today.

[alsar]

I checked it and composer will install and load only the require-dev packages defined the root package.

[gossi]

Hum, as I'd love to add this, I don't know how to detect whether install --dev or --no-dev is run. I asked on the composer-dev list if this is possible somehow: https://groups.google.com/forum/#!topic/composer-dev/LVmS3FtfaVs

[gossi]

depends on composer/composer#3008

[alsar]

Why do you need to know if the install/update is run with or without --no-dev?
Is the information available in the composer.lock not sufficient?

[gossi]

Unfortunately, no. The only interessting part is autoload-dev. So, if you have no require-dev dependencies, then I can't look whether --dev or --no-dev is run and which path to include in the buildpath or not. The alternative is to include autoload-dev no matter what.

[bgaillard]

The alternative is to include autoload-dev no matter what.

Hi, as the Composer Eclipse Plugin is mostly used for development IMO it would be great to include autoload-dev paths in the PHP Build Path by default.

Perhaps adding a checkbox like Include autoload-dev in PHP Build Path in the Composer section of the project settings could also be a good solution ?

[gossi]

autoload-dev should be loaded, no matter what. Since I've collected more experience on that, I can say that for sure, now. At the moment the composer plugin makes its move to PDT and this will be added, when the move is done.

[bgaillard]

@gossi 👍 ok great, thanks for your reactivity on this !