Grails 2.2.x未解决的依赖关系,没有任何更改以前的工作生成 [英] Grails 2.2.x unresolved dependencies without any changes to previously working build

查看:129
本文介绍了Grails 2.2.x未解决的依赖关系,没有任何更改以前的工作生成的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个Grails 2.2.4项目,我正在寻找一些工作。



当我尝试运行 grails clean 时,它已经完成了六个月的工作, code>现在我收到了一系列未解决的相关内容错误。尽管所有的依赖关系在几个月前都运行良好。在库的那一段时间内有什么改变?



我已经将BuildConfig.groovy中的日志级别更改为 logwarn,如错误消息所示。有趣的是,当我尝试通过浏览器下载构建试图解决的一些URL时,它们可以正常下载。

  ==== grailsCentral:试用
$我不确定为什么生成过程无法下载。 b $ b http://grails.org/plugins/grails-quartz/tags/RELEASE_1.0.2/quartz-1.0.2.pom

- artifact org.grails.plugins#quartz; 1.0 .2!quartz.zip:

http://grails.org/plugins/grails-quartz/tags/RELEASE_1.0.2/grails-quartz-1.0.2.zip
code>

以下是用于解决此问题的所有依赖关系:

  :::::::::::::::::::::::::::::::::::::: :::::::: 

::未解约依赖::

:::::::::::::::::::: ::::::::::::::::::::::::::

:: org.grails.plugins#asset-pipeline; 2.1.3:找不到

:: org.grails.plugins#less-asset-pipeline; 2.0.8:not found

:: org.grails.plugins#rest; 0.8:找不到

:: org.gr ails.plugins#quartz; 1.0.2:找不到

:::::::::::::::::::::::::::::: ::::::::::::::::


解决方案它看起来像2.2中提供的默认grails回购现在不起作用。我们通过将以下行添加到BuildConfig.groovy文件中的 grails.project.dependency.resolution 闭包中来解决此问题:

  grails.project.dependency.resolution = {
/ **现有资料** /
资源库{
/ **其他回购留在这里** /

// --------新增加以下内容-------- // // b $ b mavenRepohttp:// repo .grails.org / grails / repo /
}
...
}


We have a Grails 2.2.4 project that I was looking to do some work on. There has been no work done on it for six months, but it built just fine back then.

When I try to run grails clean now I get a host of UNRESOLVED DEPENDENCIES errors. This is despite all dependencies working just fine a few months ago. Has something changed within that time on the repository side?

I have changed the log level within BuildConfig.groovy to log "warn" as suggested by the error message. The interesting thing from this is when I try to download via a browser some of the URLs that the build tries to resolve, they download fine. I'm not sure why the build process can't download.

 ==== grailsCentral: tried

          http://grails.org/plugins/grails-quartz/tags/RELEASE_1.0.2/quartz-1.0.2.pom

          -- artifact org.grails.plugins#quartz;1.0.2!quartz.zip:

          http://grails.org/plugins/grails-quartz/tags/RELEASE_1.0.2/grails-quartz-1.0.2.zip

Here are all the dependencies that used to resolve that don't now:

                ::::::::::::::::::::::::::::::::::::::::::::::

                ::          UNRESOLVED DEPENDENCIES         ::

                ::::::::::::::::::::::::::::::::::::::::::::::

                :: org.grails.plugins#asset-pipeline;2.1.3: not found

                :: org.grails.plugins#less-asset-pipeline;2.0.8: not found

                :: org.grails.plugins#rest;0.8: not found

                :: org.grails.plugins#quartz;1.0.2: not found

                ::::::::::::::::::::::::::::::::::::::::::::::

解决方案

It looks like the default grails repo provided in 2.2 does not work now. We fixed this issue by adding the following line to the grails.project.dependency.resolution closure in the BuildConfig.groovy file:

grails.project.dependency.resolution = {
    /** Existing stuff here **/
    repositories {
        /** Other repos stay here **/

        //--------  NEW REPO TO ADD IS BELOW --------//
        mavenRepo "http://repo.grails.org/grails/repo/"
    }
    ...
}

这篇关于Grails 2.2.x未解决的依赖关系,没有任何更改以前的工作生成的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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