From our blog:
I just noticed that composer does not install ''dev deps. If you are using IDE for composer install, you probably want dev dependencies, so it should run composer.phar install --dev
What about 'update' command?
@umpirsky: Can you please tell us what the ideal state (--dev, --require-dev etc.) should be?
Since we need more info, waiting for your comment. SImply reopen this issue.
First, thanks for opening a new bug.
I didn't understand question regarding ideal state, but here is what I think is nice to add.
I think both install and update should include --dev option, which will install/update dev dependencies if any. Also, there is a possibility to update only particular package with:
composer.phar update ns/package
So, it would be nice to support this.
Also, there is:
composer.phar require ns/package
command, it would be nice to add support for this as well.
Thanks for your immediate comment!
(In reply to comment #4)
> First, thanks for opening a new bug.
Nothing to thank for.
> I didn't understand question regarding ideal state, but here is what I think
> is nice to add.
The ideal state is - well, the ideal state :) I mean for you, our users. In other words, how the integration should work and look like exactly.
> I think both install and update should include --dev option, which will
> install/update dev dependencies if any.
My question is - always? Would it work for everyone? Or should this be configurable? If yes then - in IDE Options or per project?
> composer.phar update ns/package
Submit a new enhancement for it, please.
> composer.phar require ns/package
Again, submit a new enhancement for it, please.
I'm not sure if I understand you corretly. At this https://blogs.oracle.com/netbeansphp/resource/article_images/composer-02.png screenshot is only install/update commands. But composer supports DEV dependencies (like PHPUnit etc.) and this dependencies installed only if you tell to commposer (via --dev flag).
So should be add install --dev and update --dev command to context menu.
(In reply to comment #5)
> > I think both install and update should include --dev option, which will
> > install/update dev dependencies if any.
> My question is - always? Would it work for everyone? Or should this be
> configurable? If yes then - in IDE Options or per project?
Well, I'm not sure. When you use composer from command line interface, you can decide if you want dev deps or not. For me it's fine to always install dev deps since I will use NetBeans to install deps in dev environment. I mean, how much does it have sense to install deps with NetBeans on production? But, if you want to get most of composer you can make it possible to choose if you want dev deps or not (popup or separate option install/update and install/update --dev).
> > composer.phar update ns/package
> Submit a new enhancement for it, please.
> > composer.phar require ns/package
> Again, submit a new enhancement for it, please.
Will submit them later, thanks.
So, I will add 2 more actions to the Composer menu:
Please, speak up if it is not OK for you.
Thanks for your comments.
Fixed, please verify if possible.
Integrated into 'main-golden', will be available in build *201211060001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Tomas Mysik <email@example.com>
Log: #221460 - Install dev dependencies by default