Use case
While working with different grails versions and a maven repository in the background I faced some weird problems regarding version problems which IDEA was complaining about.
Incident
The stacktrace looked as follow:
[INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] org.grails.maven.plugin.AbstractGrailsMojo.runGrailsInline(Ljava/lang/String;Ljava/lang/String;Z)V [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.NoSuchMethodError: org.grails.maven.plugin.AbstractGrailsMojo.runGrailsInline(Ljava/lang/String;Ljava/lang/String;Z)V at org.grails.maven.plugin.GrailsExecMojo.execute(GrailsExecMojo.java:51) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] ------------------------------------------------------------------------ [INFO] Total time: 11 seconds [INFO] Finished at: Wed Sep 05 10:44:12 CEST 2012 [INFO] Final Memory: 33M/743M [INFO] ------------------------------------------------------------------------ java.lang.NullPointerException at org.jetbrains.groovy.grails.rt.Agent$2.run(Agent.java:99) at java.lang.Thread.run(Thread.java:662) IDEA hook: Grails not found!
Neither grails clean, nor any re-builds vanished this problem.
Solution
After searching the web I could figure out that it has to with the JARs handling and cache of both grails and IDEA.
- http://youtrack.jetbrains.com/issue/IDEA-86261
- http://grails.1312388.n4.nabble.com/Can-not-create-GDK-in-Intellij-IDEA-11-with-2-1-RC1-But-no-problem-while-use-2-0-3-td4628641.html
- http://youtrack.jetbrains.com/issue/IDEA-86250
- http://stackoverflow.com/questions/11980623/sync-error-on-a-grails-project-in-intellij
- http://devnet.jetbrains.net/thread/437217
Finally, after removing the .ivy2- and maven-cache the problem did not occur anymore.
At Seha Garden International Hospital, our Stroke Rehabilitation program helps survivors relearn skills that are lost following a stroke. Through a goal-oriented treatment plan that involves physical medicine, psychiatry, Ayurveda, physiotherapy, occupational and speech therapies, our cross-functional team works together to teach stroke patients new ways of performing tasks so they can regain independence and improve their quality of life.
https://sehagarden.com/treatments/stroke-rehabilitation/
It is pleasant to scan your post and you offer sensible info. If its all identical to you retain posting such quite illuminating stuff. attention-grabbing article share and this web log is motivates additional folks to examining that web log.