Wording: Please re-run Magento compile command - Incorrect command name

[apiuser]

Feature request from tkn98, posted on GitHub Jul 06, 2016

Steps to reproduce

1. Install Magento from develop branch.
2. After all Modules are installed, a message is shown in green letters on the last line. Read that message.

The message says:

Please re-run Magento compile command

It can be greatly improved by removing the inaccuracy as there is no such command named "compile". The command name is "setup:di:compile".

This should be trivial to fix.

[apiuser]

Comment from grasdaggel, posted on GitHub Jul 06, 2016

Isn't the setup:static-content:deploy command meant with that? For developer envs its not mandatory to run di:compile each time you setup:upgrade.

[apiuser]

Comment from tkn98, posted on GitHub Jul 06, 2016

@grasdaggel: The command named "setup:static-content:deploy" does not contain the word "compile", so by wording alone already I would assume it is not meant by that.

[apiuser]

Comment from didineedthis, posted on GitHub Jul 06, 2016

No need to run "bin/magento setup:di:compile" if your developing your site just run the upgrade and "bin/magento setup:static-content:deploy" then run "bin/magento indexer:reindex" you only have to decompile when you set production mode

[apiuser]

Comment from grasdaggel, posted on GitHub Jul 06, 2016

So we are even that there is no need to run di:compile on developer environments, right? Maybe Devs can add a check which mode is set, and if its Dev, hide this message (since it doesn't do anything useful on Dev Mode), while its necessary to do so on live systems.

[apiuser]

Comment from didineedthis, posted on GitHub Jul 06, 2016

run this to check what mode you are in bin/magento deploy:mode:show

you will more than likely be in Default mode.

then set either developer or production

1.bin/magento deploy:mode:set production

1. bin/magento deploy:mode:set developer

Once you leave default mode there is no going back to it.

[apiuser]

Comment from tkn98, posted on GitHub Jul 06, 2016

It's all fine what you guys write here, but I'm more concerned about the message given and that it is not showing the concrete command intended to run. The discussion shows, that there are diverse scenarios in which the one or other command, also additionally, needs to be (not) run (at all). But please do not derail this report which is about the message missing the concrete command name.

[apiuser]

Comment from tkn98, posted on GitHub Jul 08, 2016

And just a short note: setup:di:compile performs checks on your di configuration. I guess this is useful in development mode, too from time to time.