 |
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Barry Kaplan - 09 Dec 08 02:58
What does v2.0 mean? I only see 0.8 in the plugin manager.
Sorry, the version number is 8.0. So now I really don't know what the version numbers mean. Is a different version numbering scheme used for jira than in the plugin manager?
The latest 8.1 EAP build (9572) does seem to register the grails-1.1-beta1 server correctly now. However, on startup, it generates a ClassNotFoundException.
Exception in thread "main" java.lang.ClassNotFoundException: org.codehaus.groovy.grails.cli.support.GrailsStarter
Looking at the startup command line in the Run window, I noticed that for the 1.1 Grails server, Intellij is no longer including "dist\grails-cli-1.0.4.jar" in the classpath. I believe that jar was possibly merged in to the "grails-bootstrap-1.1-beta1.jar", though I'm not positive. Let me know if you'd prefer I submit a new issue ticket for this. Fixed. Check the next EAP or build the plugin from sources
Not fixed for me I just got EAP 9572 and trying to run gives:
"C:\Program Files\Java\jdk1.6.0_11\bin\java" -Dserver.host=localhost -Dserver.port=8080 -Denable.jndi=false -Ddisable.auto.recompile=false -Drecompile.frequency=3 -Xmx256M -Dgrails.home=C:\DEVTOOLS\grails-1.1-beta2 -Dbase.dir=C:\DEVELOPMENT\IntelliJ\T11 "-Dtools.jar=C:\Program Files\Java\jdk1.6.0_11\lib\tools.jar" -Dgroovy.starter.conf=C:\DEVTOOLS\grails-1.1-beta2/conf/groovy-starter.conf -Didea.launcher.port=7532 "-Didea.launcher.bin.path=C:\Program Files\JetBrains\IntelliJ IDEA 9572\bin" -Dfile.encoding=windows-1252 -classpath "C:\DEVTOOLS\grails-1.1-beta2\lib\groovy-all-1.6-RC-1.jar;C:\Program Files\JetBrains\IntelliJ IDEA 9572\lib\idea_rt.jar" com.intellij.rt.execution.application.AppMain org.codehaus.groovy.grails.cli.support.GrailsStarter --main org.codehaus.groovy.grails.cli.GrailsScriptRunner --conf C:\DEVTOOLS\grails-1.1-beta2/conf/groovy-starter.conf --classpath C:\DEVTOOLS\grails-1.1-beta2\lib\groovy-all-1.6-RC-1.jar;. run-app It seems that the grails jars are being left out of the runner's classpath. See also: http://grails.markmail.org/message/zhggdwwbwfaywvgk #9572 was built 16.12, which is earlier than my fix. I hope the next EAP will be in this year.
I was having all the problems described in people's comments, but finally got things working. I'll describe the fix for the last problem since the other problems have already been covered. When the "Run Grails" from inside the IDEA fails, I'm not sure if this is a grails issue or jetgroovy, but for whatever reason the ${grails.version} in groovy-starter.conf isn't working. So you need to explicitly define the file name in GRAILS_HOME/conf/groovy-starter.conf. And of course have the correct jetgroovy plugin. So the line below works for me using IDEA EAP 9572 + jetgroovy 21538 + grails 1.1-beta2.
load ${grails.home}/dist/grails-bootstrap-1.1-beta2.jar I'm getting this error too. I am using EAP 9618 and tried to fix it like Tyler said. But without luck. This only happens when I try to run the integration/unit tests.
It seems that there is missing grails-bootstrap-1.1-beta2.jar. My workaround for this is finally to add a single module library (module settings->modules->dependencies->path_to_grails-bootstrap-1.1-beta2.jar) directly. This works fine so far... Issues with recognizing bootstrap jar and Grails tests will be fixed in next 8.1 EAP, thank you
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Blocker
JetGroovy chokes on Grails 1.1 SDK
