grails - 解决获取依赖项的错误:找不到工件,Grails

标签 grails grails-plugin

我将插件compile 'org.grails.plugins:spring-security-core:3.1.1'添加到我现有的Grails 2.4.4项目中。当我从GGTS下载源jar或刷新依赖项时,出现如下错误。

Resolve error obtaining dependencies: Could not find artifact org.grails.plugins:spring-security-core:zip:3.1.1 in grailsCentral (https://repo.grails.org/grails/plugins) (Use --stacktrace to see the full trace)
Error |
Resolve error obtaining dependencies: Could not find artifact org.grails.plugins:spring-security-core:zip:3.1.1 in grailsCentral (https://repo.grails.org/grails/plugins) (Use --stacktrace to see the full trace)
Error |

我尝试取消评论
 mavenRepo  "http://repository.codehaus.org"
 mavenRepo "http://download.java.net/maven/2/"
 mavenRepo "http://repository.jboss.com/maven2/"

并尝试了
 mavenRepo "https://repo.grails.org/grails/core" or mavenRepo "http://repo.grails.org/grails/core"

我还尝试了一些stackoverflow问题中给出的解决方案。但是并没有解决我的错误。有人有解决方案吗?
我的BuildConfig.grovvy如下
grails.servlet.version = "3.0" // Change depending on target container compliance (2.5 or 3.0)
grails.project.class.dir = "target/classes"
grails.project.test.class.dir = "target/test-classes"
grails.project.test.reports.dir = "target/test-reports"
grails.project.work.dir = "target/work"
grails.project.target.level = 1.6
grails.project.source.level = 1.6
//grails.project.war.file = "target/${appName}-${appVersion}.war"

grails.project.fork = [
    // configure settings for compilation JVM, note that if you alter the Groovy version forked compilation is required
    //  compile: [maxMemory: 256, minMemory: 64, debug: false, maxPerm: 256, daemon:true],

    // configure settings for the test-app JVM, uses the daemon by default
    test: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, daemon:true],
    // configure settings for the run-app JVM
    run: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, forkReserve:false],
    // configure settings for the run-war JVM
    war: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, forkReserve:false],
    // configure settings for the Console UI JVM
    console: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256]
]

grails.project.dependency.resolver = "maven" // or ivy
grails.project.dependency.resolution = {
    // inherit Grails' default dependencies
    inherits("global") {
        // specify dependency exclusions here; for example, uncomment this to disable ehcache:
        // excludes 'ehcache'
    }
    log "error" // log level of Ivy resolver, either 'error', 'warn', 'info', 'debug' or 'verbose'
    checksums true // Whether to verify checksums on resolve
    legacyResolve false // whether to do a secondary resolve on plugin installation, not advised and here for backwards compatibility

    repositories {
        inherits true // Whether to inherit repository definitions from plugins

        grailsPlugins()
        grailsHome()
        mavenLocal()
        grailsCentral()
        mavenCentral()
        // uncomment these (or add new ones) to enable remote dependency resolution from public Maven repositories
//        mavenRepo "http://repository.codehaus.org"
//        mavenRepo "http://download.java.net/maven/2/"
//        mavenRepo "http://repository.jboss.com/maven2/"


    }

    dependencies {
        // specify dependencies here under either 'build', 'compile', 'runtime', 'test' or 'provided' scopes e.g.
        // runtime 'mysql:mysql-connector-java:5.1.29'
        // runtime 'org.postgresql:postgresql:9.3-1101-jdbc41'
        test "org.grails:grails-datastore-test-support:1.0.2-grails-2.4"
    }

    plugins {
        // plugins for the build system only
        build ":tomcat:7.0.55"

        // plugins for the compile step
        compile ":scaffolding:2.1.2"
        compile ':cache:1.1.8'
        compile ":asset-pipeline:1.9.9"

        // plugins needed at runtime but not for compilation
        runtime ":hibernate4:4.3.6.1" // or ":hibernate:3.6.10.18"
        runtime ":database-migration:1.4.0"
        runtime ":jquery:1.11.1"

        // Uncomment these to enable additional asset-pipeline capabilities
        //compile ":sass-asset-pipeline:1.9.0"
        //compile ":less-asset-pipeline:1.10.0"
        //compile ":coffee-asset-pipeline:1.8.0"
        //compile ":handlebars-asset-pipeline:1.3.0.3"
        compile 'org.grails.plugins:spring-security-core:3.1.1'
    }
}

最佳答案

Grails 2.x插件每个在grails.org的“插件门户”中都有一个页面,该插件的页面位于http://grails.org/plugin/spring-security-core。就像那里所说的,最新版本是2.0.0,因此您应该添加

compile ':spring-security-core:2.0.0'

在BuildConfig.groovy的“插件”部分中。

或者,如果您确实要使用3.1.1版,请升级您的应用程序以使用Grails 3.x(这是读者的练习),然后在升级后的应用程序的build.gradle文件中添加v3.1.1的依赖项。

Grails 3插件页面位于Grails站点的另一部分中,而与Grails 3兼容的spring-security-core插件的页面位于https://grails.org/plugins.html#plugin/spring-security-core

2.0.0和3.1.1插件文档均可在https://grails-plugins.github.io/grails-spring-security-core/上获得

关于grails - 解决获取依赖项的错误:找不到工件,Grails,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/38715241/

相关文章:

grails - 动态Groovy上传到Grails应用程序

hibernate - grails withSession 和当前的 hibernate session

grails - Grails Spring Security如何自定义(或添加)其他身份验证规则

java - 如何使用 grails 1.3.2 和插件 spring-security-core 1 实现自定义 FilterSecurityInterceptor?

grails - authenticatedUser 为 null 但原则不为 null

grails - 无法安装Grails 2.4.4本地插件(zip文件)

grails - 记录/Log4J到数据库

grails - Grails ehcache插件编译错误

spring - 从src/groovy中的类获取对spring bean的引用

session - GRAILS:如何通过Spring Security核心插件获取当前登录用户的数量?