New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use composer for dependency management #11
Comments
Thanks Lucas. We will reschedule the implementation of composer for dependency management to Shopware 4.1.0 |
+1 For Composer. @lsmith77 Do you know about resources / best practices how to maintain patches for composer managed dependencies? Some of our patches won't be included in upstream projects so we have to apply them right after composer.phar install / update. Are there any hooks etc. available to archive this without requiring a separate ant/phing build-script? |
you can always override a remote repo with a specific one inside your composer.json |
+1 For Composer. |
The (post-install-cmd)-Composer Scripts took my attention. Composer is definitive on the radar for the 4.1 Release. |
It would be great, if composer comes with the release of version 4.1. This would simplify our development extremely. |
Well, I'll do my very best ;) |
everthing is better with composer (bluetooth) 👍 |
👍 |
…o master * commit '5e5316f446c4c885456b44f83bc79ddd36fa5432': SW-5050 - Remove generated attribute models from repository
There is still no composer support in version 4.1.2 .. when do plan on implementing this? |
Hi @mrmaxon, as far as I know, this is currently not scheduled for a release. Please vote and comment here, so we can push this a bit :) => http://jira.shopware.de/?ticket=sw-6989 |
Hi, thanks for opening this issue. In order to have all issues at one place, we've decided to move the GitHub issues to our own bug tracker which can be found at http://jira.shopware.de. Your ticket can be found at the following url: |
No description provided.
The text was updated successfully, but these errors were encountered: