简体繁体 English

Grails maven插件想要Groovy 2.4.2

[英]Grails maven plugin wants Groovy 2.4.2

原文 2014-06-30 13:25:06 5 1 java/ maven/ grails/ groovy

I upgrade to Grails 2.4.2 because that supposedly fixes a bug with the maven plugin that caused it to generate a bad pom.xml file. 我升级到Grails 2.4.2，因为据说修复了maven插件的一个错误，导致它生成一个糟糕的pom.xml文件。 Now, when I try to run the 2.4.2-generated pom with mvn clean install I get the following error message: 现在，当我尝试使用mvn clean install运行2.4.2生成的pom时，我收到以下错误消息：

[ERROR] Failed to execute goal org.grails:grails-maven-plugin:2.4.2:maven-compile (default-maven-compile) on project PROJECT : Failed to create classpath for Grails execution. [错误]无法执行目标org.grails：grails-maven-plugin：2.4.2：项目PROJECT上的maven-compile（default-maven-compile）：无法为Grails执行创建类路径。 Failure to find org.codehaus.groovy:groovy-all:jar:2.4.2 in https://REPO was cached in the local repository, resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced -> [Help 1] 未能找到org.codehaus.groovy： https://REPO groovy-all：jar：2.4.2 https://REPO缓存在本地存储库中，在nexus的更新间隔过去或强制更新之前，不会重新尝试解析 - > [帮助1]

Groovy 2.4.2 obvious doesn't exist since 2.3.X is the latest release. Groovy 2.4.2显然不存在，因为2.3.X是最新版本。 How do I force the maven plugins to take 2.3.2's groovy-all package as the dependency to use for Groovy? 如何强制maven插件将2.3.2的groovy-all包作为Groovy使用的依赖？

1 个解决方案

Solution: it was a bug in the Maven plugin. 解决方案：这是Maven插件中的一个错误。 I sent a code fix to the owner. 我向代理人发送了代码修复程序。

Update : I sent a bug fix that was incorporated into Grails. 更新：我发送了一个包含在Grails中的错误修复程序。 The new dependency is org.grails:grails-maven-plugin:2.4.3 . 新的依赖项是org.grails:grails-maven-plugin:2.4.3 。 You should update your Grails BuildConfig and the pom file (or regenerate it). 您应该更新Grails BuildConfig和pom文件（或重新生成它）。