Thomas Gossmann

looks like some `monitor.done()` calls aren't made. Keep an eye under which circumstances this happens.

When composer exits with an error.

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...

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...

depends on composer/composer#3008

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...

`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...

There are two locations where you can configure which composer.phar to use: 1) Eclipse Preferences > Composer: Select the php binary + composer binary 2) Project Properties > Composer: Override...

Depends on #106

Here is a concept mock up: