Feeling Lucky
?
?
[#16896] - Run composer in optimized mode
- Fixed in Code Base
- 10 Aug 2017
- Medium
- Build: staging
- # 16896
- Diff
- Digital-Peak:j3/optimize-composer
- Success hound No violations found. Woof! Details
- Success continuous-integration/drone/pr the build was successful Details
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
- Success continuous-integration/appveyor/pr AppVeyor build succeeded Details
User tests: Successful: Unsuccessful:
Pull Request for Issue #16881.
Summary of Changes
Composer has an optimized mode, where they recommend to use in production. More information can be found in the composer documentation.
This pr activates that mode, which leads to bigger class map files and less IO. More infromation can be found in issue #16881.
Testing Instructions
Just log in on the back end and open some articles on the front end.
Expected result
All should work as expected, just faster.
Actual result
All should work as expected.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | External Library Libraries |
| Category | External Library Libraries | ⇒ | External Library Composer Change Libraries |
laoneo
- comment
- 28 Jul 2017
I can run then another composer install, no worries.
laoneo
- comment
- 10 Aug 2017
Merged with staging too.
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-08-10 23:36:05 |
| Closed_By | ⇒ | mbabker |
As with the merge of #16754, this one can safely be merged, as a composer install in optimized mode was run there. This pr only adds the required configuration option to the composer.json file that the next
composer updatewill not overwrite the optimized classmap files.I did another
composer installand there are some test classes showing up in the diff which should not being mapped.