当前位置: 首页 > 知识库问答 >
问题:

在Ubuntu上使用Grails Gradle插件:未找到Grails

秦毅
2023-03-14

我目前正在尝试使用Gradle构建一个Grails项目,以轻松集成一些存储库。我已经创建了一个新的目录,并从该目录我已经创建了以下build.gradle文件从这个网站的指示:

http://grails.github.io/grails-gradle-plugin/docs/manual/guide/introduction.html

buildscript {
    repositories {
       jcenter()
    }
    dependencies {
        'org.grails:grails-gradle-plugin:2.1.0'
    }
}

apply plugin: 'grails'

grails {
    grailsVersion = '2.4.0' // Specifies the Grails version to use
    groovyVersion = '2.3.1' // Specify the Groovy version to use (should match the version that ships with the above Grails version)
    springLoadedVersion = '1.2.0.RELEASE' // Specify the Spring Loaded version to use
}

repositories {
    jcenter()
    grails.central() //Adds the Grails Central Repository for resolving Grails plugins (replaces grailsPlugins(), grailsCentral() from BuildConfig.groovy)
}

dependencies {
    bootstrap 'org.grails.plugins:tomcat:7.0.50.1'

    compile 'org.grails.plugins:scaffolding:2.0.2'
    compile 'org.grails.plugins:cache:1.1.1'

    runtime 'org.grails.plugins:hibernate:3.6.10.8' //or 'org.grails.plugins:hibernate4:4.3.1.1'
    runtime 'org.grails.plugins:database-migration:1.3.8'
    runtime 'org.grails.plugins:jquery:1.11.0'
    runtime 'org.grails.plugins:resources:1.2.2'

    //runtime 'mysql:mysql-connector-java:5.1.24'
    //runtime 'org.postgresql:postgresql:9.3.1100-jdbc41'

    //Additional resources capabilities
    //runtime 'org.grails.plugins:zipped-resources:1.0.1'
    //runtime 'org.grails.plugins:cached-resources:1.1'
    //runtime 'org.grails.plugins:yui-minify-resources:0.1.5'

    //Alternate to the resources plugin
    //compile 'org.grails.plugins:asset-pipeline:1.5.0'

    //Additional asset-pipeline capabilities
    //compile 'org.grails.plugins:sass-asset-pipeline:1.5.1'
    //compile 'org.grails.plugins:less-asset-pipeline:1.5.0'
    //compile 'org.grails.plugins:coffee-asset-pipeline:1.5.0'
    //compile 'org.grails.plugins:handlebars-asset-pipeline:1.0.0.3'
}

当我尝试使用gradle init构建时,我遇到了以下错误:

失败:构建失败,有一个异常。

>

  • 其中:构建文件'/home/ian/grailsDir/deadness/Build。格雷德尔线:10

    出了什么问题:在评估根项目“死亡”时出现了一个问题。

    找不到id为“grails”的插件。

    如何获得Grails插件?我目前运行Grails 2.5.0和Gradle 2.4。我也用早期版本的Grails尝试过。

    堆栈跟踪是:

    * Exception is:
    org.gradle.api.GradleScriptException: A problem occurred evaluating root project 'deadness'.
        at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:76)
        at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl$1.run(DefaultScriptPluginFactory.java:148)
        at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:156)
        at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:39)
        at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:26)
        at org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:34)
        at org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:55)
        at org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:487)
        at org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:85)
        at org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:42)
        at org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:35)
        at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:129)
        at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:106)
        at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:86)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:90)
        at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)
        at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:41)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:28)
        at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:50)
        at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:27)
        at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:40)
        at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:169)
        at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:237)
        at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:210)
        at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)
        at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
        at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:206)
        at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)
        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
        at org.gradle.launcher.Main.doAction(Main.java:33)
        at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
        at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:54)
        at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:35)
        at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
    Caused by: org.gradle.api.plugins.UnknownPluginException: Plugin with id 'grails' not found.
        at org.gradle.api.internal.plugins.DefaultPluginManager.apply(DefaultPluginManager.java:110)
        at org.gradle.api.internal.plugins.DefaultObjectConfigurationAction.applyType(DefaultObjectConfigurationAction.java:113)
        at org.gradle.api.internal.plugins.DefaultObjectConfigurationAction.access$200(DefaultObjectConfigurationAction.java:36)
        at org.gradle.api.internal.plugins.DefaultObjectConfigurationAction$3.run(DefaultObjectConfigurationAction.java:80)
        at org.gradle.api.internal.plugins.DefaultObjectConfigurationAction.execute(DefaultObjectConfigurationAction.java:136)
        at org.gradle.api.internal.project.AbstractPluginAware.apply(AbstractPluginAware.java:46)
        at org.gradle.api.plugins.PluginAware$apply.call(Unknown Source)
        at org.gradle.api.internal.project.ProjectScript.apply(ProjectScript.groovy:34)
        at org.gradle.api.Script$apply$0.callCurrent(Unknown Source)
        at build_cgy5iob1jp300dugadkqvpnyl.run(/home/ian/grailsDir/deadness/build.gradle:10)
        at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:74)
        ... 35 more
    
  • 共有1个答案

    长孙谦
    2023-03-14

    请注意以下代码。。。

    dependencies {
        'org.grails:grails-gradle-plugin:2.1.0'
    }
    

    ...应该是:

    dependencies {
        classpath 'org.grails:grails-gradle-plugin:2.1.0'
    }
    

    这必须解决问题。

     类似资料:
    • 我已经使用pip命令安装了locust,当我继续使用这个命令验证安装时:locust-v,它会返回以下行:命令未找到 其次,当我安装Locust时,控制台上显示了一些语句,如所附图片所示。请分享解决方案! 在此处输入图像描述

    • 请注意:这不是重复的。我想让Gradle的IDEA插件为我正确配置IntelliJ IDEA CE项目。我对任何涉及手动调优IntelliJ以找到我的JDK的解决方案都不感兴趣。这是一个Gradle IDEA插件功能,可以而且应该工作。 如果你能找到另一个问题,包括正确地让Gradle IDEA插件配置IntelliJ(在Mac上运行),以便它可以找到JDK 8,那么请务必将其标记为dupe,并提

    • 在安装requirements.txt文件之前,我一直在跟踪文档。在尝试安装第6行“psycopg2==2.5.3”时,它总是失败。信息是这样的-- 当然我找到了几个关于这个的帖子。所以我开始检查东西。我相信mac的postgres应用程序随PsycopG2一起提供。我已经将postgres添加到我的路径中,并签入运行“echo$path”的终端。我没有任何其他旧版本冲突。postgres文档说我

    • 大家好,我需要一个解决方案laravel项目,当我尝试打开后端管理与 /control它给我一个错误"未找到-请求的资源 /control未在该服务器上找到。" 当我将名称"/Control"更改为"/Control5"或类似的东西时,它的工作正常,但问题是我使用 /control视图和其他!我是新来的laravel我不知道是什么问题?请帮我解决这个问题! 网状物php 仪表板控制器

    • 问题内容: 有没有办法确定您的package.json文件中是否有不再需要的软件包? 例如,当尝试一个软件包并在以后注释或删除代码但忘记卸载它时,我最终得到了几个可以删除的软件包。 确定包是否可以安全删除的有效方法是什么? 问题答案: 您可以使用称为depcheck的npm模块(至少需要Node版本10)。 安装模块: 运行它并找到未使用的依赖项: 这种方法的好处是您不必记住or 命令。 要运行