升级到Laravel 4.1错误 [英] Upgrade to Laravel 4.1 error

查看:81
本文介绍了升级到Laravel 4.1错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我相信我已经为4.1准备好了所有依赖项,但是使用composer update时出现以下错误:

I believe I have all my dependencies ready for 4.1, but I get the following errors when I use composer update:

生成自动加载文件

脚本php artisan进行了明确编译,处理了返回错误的post-update-cmd事件:

Script php artisan clear-compiled handling the post-update-cmd event returned with an error:

脚本php artisan优化处理错误返回的post-update-cmd事件:

Script php artisan optimize handling the post-update-cmd event returned with an error:

我的作曲家文件如下:

{

"require": {

    "laravel/framework": "4.1.*",
    "jasonlewis/basset": "dev-master",
    "twbs/bootstrap": "dev-master",
            "frozennode/administrator": "dev-master",
            "bllim/datatables": "*",
            "scubaclick/mandrill": "dev-develop"
},
"require-dev": {
    "codeception/codeception": "1.8.*",
    "way/generators": "dev-master"
},
"autoload": {
    "classmap": [
        "app/commands",
        "app/controllers",
        "app/database/migrations",
        "app/database/seeds",
        "app/tests/TestCase.php",
        "app/Acme/Apis/v1"
    ],
    "psr-0": {
        "Acme" : "app/"
    }
},
"scripts": {
    "post-install-cmd": [
        "php artisan optimize"
    ],
    "post-update-cmd": [
        "php artisan clear-compiled",
        "php artisan optimize"
    ],
    "post-create-project-cmd": [
        "php artisan key:generate"
    ]
},
"config": {
    "preferred-install": "dist"
},
"minimum-stability": "dev"

}

推荐答案

您可能需要执行composer update --no-scripts来更新所有作曲家文件,而无需运行artisan命令;原因是直到作曲家完成技工后,升级操作才会被破坏,并且默认的composer.json文件已将命令php artisan clear-compiled设置为在更新供应商文件夹之前运行.

You would have needed to do composer update --no-scripts to update all your composer files without running the artisan commands; the reason for this is until composer has finished artisan would be broken by the upgrading and the default composer.json file has the command php artisan clear-compiled set to run before the vendor folder is updated.

如果其他所有方法均失败,则删除供应商目录和composer.lock文件,然后运行composer install

If all else fails then delete your vendor directory and the composer.lock file and then run composer install

这篇关于升级到Laravel 4.1错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆