[GRADLE-2264] java.lang.NoClassDefFoundError: groovy/lang/GroovyObject Created: 01/May/12 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 1.0-rc-3 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Steve Holmes | Assignee: | René Gröschke (Inactive) |
| Resolution: | Won't Fix | Votes: | 4 |
| Description |
|
Here is the Stacktrace. I got this when building using the grails-gradle plugin. 18:22:13.629 [ERROR] [org.gradle.BuildExceptionReporter] FAILURE: Build failed with an exception. |
| Comments |
| Comment by René Gröschke (Inactive) [ 07/May/12 ] |
|
What version of grails, and what version of the grails-gradle-plugin do you use? |
| Comment by Steve Holmes [ 07/May/12 ] |
|
I'm using grails 2.0.1 and I'm not certain of the version of the grails-gradle plugin but I think it was 1.1.1-SNAPSHOT. It was the latest version when I filed the bug but I just noticed that Graeme Rocher made some changes 5 days ago and I don't know if I was using those changes. It doesn't look like the version was incremented. |
| Comment by René Gröschke (Inactive) [ 13/May/12 ] |
|
Hello Steve, regards, |
| Comment by Dror Bereznitsky [ 13/Jun/12 ] |
|
I also get the same exception when using version 1.1.0 of the grails-gradle plugin |
| Comment by Aaron Long [ 29/Jun/12 ] |
|
I have a build.gradle using 1.1.1-SNAPSHOT which is failing with the same error. The weird thing is that some commands work and others don't. For instance, running "gradlew grails-test-app" works fine. But running "gradlew grails-war" fails with the above error. Here is my build.gradle for reference. I'm running on Windows 7, 64-bit with JVM 1.7.0_05. I'm using the gradlew wrapper version 1.0 final.
buildscript {
repositories {
maven {
url "http://repo.grails.org/grails/core/"
}
}
dependencies {
classpath "org.grails:grails-gradle-plugin:1.1.1-SNAPSHOT", "org.grails:grails-bootstrap:${grailsVersion}"
}
}
apply plugin: "groovy"
apply plugin: "grails"
repositories {
mavenCentral()
maven {
url "http://repo.grails.org/grails/core/"
}
}
dependencies {
groovy localGroovy()
compile "org.grails:grails:${grailsVersion}",
"org.grails:grails-core:${grailsVersion}",
"org.grails:grails-crud:${grailsVersion}",
"org.grails:grails-hibernate:${grailsVersion}",
"org.grails:grails-logging:${grailsVersion}",
"org.grails:grails-plugin-controllers:${grailsVersion}",
"org.grails:grails-plugin-services:${grailsVersion}",
"org.grails:grails-plugin-domain-class:${grailsVersion}",
"org.grails:grails-plugin-datasource:${grailsVersion}",
"org.grails:grails-plugin-i18n:${grailsVersion}"
}
|
| Comment by Aaron Long [ 29/Jun/12 ] |
|
Just to confirm, I get the same behavior running the gradle wrapper and gradle. |
| Comment by Scott [ 13/Jul/12 ] |
|
I also have precisely the same issue, except that no commands work at all. "test" also fails, along with all "grails-..." commands. This is using gradle directly without a wrapper. |
| Comment by Richard Dunn [ 17/Jul/12 ] |
|
I was able to build the project just fine, but I get the same error attempting to run the program. Mac OS X, 10.7.4. I am running gradle: ------------------------------------------------------------ Gradle build time: Tuesday, June 12, 2012 12:56:21 AM UTC |
| Comment by Martin Stockhammer [ 31/Jul/12 ] |
|
I have the same issue on Linux |
| Comment by john hedden [ 08/Aug/12 ] |
|
ditto for me. config: ------------------------------------------------------------ Gradle build time: Tuesday, June 12, 2012 12:56:21 AM UTC works with grails 2.0.0 but not with 2.1.0. anyone know of a work around for this? |
| Comment by Benjamin Muschko [ 15/Nov/16 ] |
|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
| Comment by Benjamin Muschko [ 10/Feb/17 ] |
|
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved. |