I encountered several issue in importing grails project
After importing my grails project with GGTS 3.4.0 I can't do anything:
The import action action freezes at 50%, so I stop it.
'Update grails dependencies' action doesn't stop so I deselect the 'Keep external Grails running' option.
Clean and compile action triggered an an exception after a while:
"Problem executing: clean
The command 'C:\Program Files\Java\jdk1.7.0_45\bin\javaw.exe (23 déc. 2013 13:52:45)' was terminated because it didn't produce new output for some time.
See details for the output produced so far.
If you think the command simply needed more time, you can increase the time limit in the Grails preferences page.
See menu Windows >> Preferences >> Grails >> Launch"
It's really frustrating I could not do anything for several hours.
This topic follows this one: Install manually grails
Try with the lower version sts 3.3.0. I know this doesn't resolve the issue which you are facing but for sake of other workaround hope this helps.
http://dist.springsource.com/release/STS/3.3.0/dist/e3.8/groovy-grails-tool-suite-3.3.0.RELEASE-e3.8.2-win32-x86_64-installer.exe
Regards..
Related
I downloaded a serverpush example called GrailsChat and trying to run is on grails 2.4.4.
I had some issues with dependencies missing that took me a while to figure out (don't think it's related but just mentioning it).
When I run grails run-app I get:
| Application metadata not found, please run: grails upgrade
When I run grails upgrade I get
| Script 'Upgrade' not found, did you mean:
1) MigrateDocs
2) IntegrateWith
3) SetGrailsVersion
4) InstallDependency
5) DependencyReport
> Please make a selection or enter Q to quit:
I figure the issue is probably to do with the grails version I have being newer than the grails version that the sample app was targetting but I don't want to move back version simply to run an example (I'd rather understand the underlying issue).
Can anyone point me to some documentation that will help me understand what the application metadata is and how to move forward please?
Grails Upgrade command is removed in 2.4. You might have to upgrade the app manually following the guide.
Or you can just run the service wrapper which will download the grails version automatically base on the app.
./grailsw run-app
It seems like you have missed any one of mentioned
Not set grails proper Version
Missing application.properties file (with proper grails version)
I'm pretty new to grails so it's possible that i've missed something obvious, but I am trying to utilise the JMS plugin. I've included the following within the plugins section of my BuildConfig.groovy
compile ":jms:1.2"
However when I compile the app I get lots of "unable to resolve class" exceptions for imports within the jms plugin (40 in total, javax.jms.* and org.springframework.jms.* mostly).
e.g.
| Error Compilation error: startup failed:
C:\dev\prj\grails\tApp\target\work\plugins\jms-1.2\grails-app\utils\DefaultJmsBe
ans.groovy: 16: unable to resolve class org.springframework.jms.listener.Default
MessageListenerContainer
# line 16, column 1.
import org.springframework.jms.listener.DefaultMessageListenerContainer
^
C:\dev\prj\grails\tApp\target\work\plugins\jms-1.2\grails-app\services\grails\pl
ugin\jms\JmsService.groovy: 22: unable to resolve class javax.jms.Message
# line 22, column 1.
import javax.jms.Message
Is anyone able to point me in the right direction? The issue can be reproduced just by adding the plugin to the BuildConfig.groovy as mentioned above to a new grails project .
Grails version 2.3.3
Many thanks
Tom
While doing a Grails 2.2 -> 2.3.4 upgrade I ran into a similar issue and was able to get things working by manually adding spring-jms to my dependencies in BuildConfig.groovy:
compile 'org.springframework:spring-jms:3.2.5.RELEASE'
It's odd that this would stop working now of course, since the jms plugin hasn't changed in a very long time. My guess is that it depends on the spring-jms lib, but didn't have it listed as a dependency, instead relying on grails to bring it in. According to the 2.3.x upgrade guide, there have been changes to what grails brings in now, so perhaps spring-jms stopped getting a free ride.
The Grails MX website has a write-up that might help; it's built using 2.3.4:
http://grails.org.mx/2013/12/20/quickstart-jms-en-grails/
It was pretty helpful to me in getting a sample application up and running. It's in Spanish though, so may need to have Google translate it for you...
Have you tried executing the command grails refresh-dependencies before running grails run-app?
I wrote a blog post on installing a Grails plugin if you need more details.
How to stop grails processes in GGTS 3.4 with grails 2.3. the stop button of GGTS is not stopping the server running and the java.exe processes are still showing in task manager.
Comment the grails.project.fork = [ .. ] part of your BuildConfig.groovy file.
This part enables running run-app, test-app and war in different threads(so you don't have to stop one to start the other), and it seems ggts isn't successfully destroying the thread right now.
For reference, here is the related issue in the ggts bug tracker https://issuetracker.springsource.com/browse/STS-3522
Can you try to disable the "Keep external Grails running" option in Eclipse Preferences -> Groovy -> Grails -> Grails Launcher?
Unchecking the "Keep external Grails running" does not work for me. What I do is to hit the "Grails Command History" icon and type "stopApp" (or pick stopApp if previously typed). Once this commands finishes executing, then you can stop the Grails application using the stop button.
Using Groovy Grails Tool Suite GGTS 3.4.0 on windows 64x. For my simple projects, the stop button works. For a bigger complex project, it does not. I use the "stop-app" (opposite of "run-app"). See: 2.8 Running an Application in the getting started guide. I think that in older versions of Grails ( < 2.x something) you had to create your own "stop-app" script. I think the newer 2.3.x has it built in.
I am using GGTS 3.5.1, Grails 2.3.8, Java1.7 over Windows configuration the command is works for me "stop-app" and "run-app"
I'm trying to get my feet wet with grails, so I'm following a tutorial to get going with a sample project. I downloaded grails 2.3.2, added the environment variables for the command prompt commands, and successfully created a project by using >grails create-app teamwork. Calling >grails run-app after changing to the project directory successfully downloads all requisites, but then I get . I know that this exception doesn't reveal much, but do you guys have any ideas on why? I am running command prompt in admin mode, if that means anything.
Try not forking the JVM in BuildConfig.groovy, if I recall correctly. If that works, then check the JIRA issues for Grails 2.3.2.
I get a strange error when I add a new property to message.properties file in my grails application during runtime. When I restart the application via the command line, or restart STS, this error disappears. I am on version 2.0.1 and until a week ago, I was able to add new properties to message.properties file during runtime. Here is the stacktrace of the error
| Error 2012-06-18 16:54:58,702 [Thread-38] ERROR plugins.AbstractGrailsPluginManager - Plugin [i18n:2.0.1] could not reload changes to file [/home/project/grails-app/i18n/messages.properties]: Error starting Sun's native2ascii:
Message: Error starting Sun's native2ascii:
Any ideas?
cd to jdk path
cp lib/tools.jar jre/lib/ext/tools.jar
It solves the issue.
Note: to get correct jdk path,
check GGTS --> Windows --> Preferences --> Java --> Installed JREs --> JREs Home Path
You should be using JDK rather than JRE.
Also, if you don't need the native2ascii (which you probably don't), in BuildConfig.groovy use: grails.enable.native2ascii = false
Very frustrating bug.
After I executed all the steps suggested above in this thread, grails app was STILL not seeing tools.jar...
GRRR!
For anyone experiencing this problem in GGTS when pointing to the 1.7 jdk (when setting the jre) persisting afterwards, you MUST do the following:
Pick the correct jdk (1.7) in the "JRE Definition" panel within "Installed JRE's" in the GGTS Preferences panels.
Watch the jars from that jdk populate in the JRE definition window panel at the bottom "JRE System Libraries".
Check for tools.jar (mine DID NOT show up as recognized within the jdk lib or, after i tried 'zawmn83's post above) in /lib/ext.
If tools.jar does not show up as recognized in the jdk, click the "Add External JARs..." button, find it, add it.
That completely solve my problem - THANK GOD!!!!
p.s. i also had to set my JAVA_HOME to my 1.7 jdk correctly, in my .bash_profile but, that's already called out here as part of the solution.
Thanks everyone for contributing on this one - this bug has been causing me brain damage whilst tinkering with it today, and the above suggestions got me 99% of the way there!
I had a similar problem, in the end I
Removed the Debug Config for the Project
Deleted the project (but NOT the files)
Removed the .settings directory
Removed the .classpath and .project files from the project
Created a New General Project with the same name in the workspace
Recreated the Debug -> Run as Run-App
Hope this helps
This happened to me when I installed java 8 in parallel with java 7 on Ubuntu but didn't properly configure it with update-alternatives. Specifically, JAVA_HOME was not set properly.
I had a similar error when compiling Grails 2 from the command line under linux.
Error packaging application: Error occurred processing message bundles: Error starting Sun's native2ascii:
...
Caused by: : Error starting Sun's native2ascii:
...
Caused by: java.lang.ClassNotFoundException: sun.tools.native2ascii.Main`
I solved it by setting JAVA_HOME to JDK as mentioned above, something like
JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.161.x86_64
and not:
JAVA_HOME=/usr/lib/jvm/jre-1.7.0-openjdk.x86_64
also include $JAVA_HOME/bin in the PATH variable
On linux, running grails war command, it solves the issue
cp /usr/lib/jvm/java-1.8.0-openjdk/lib/tools.jar /usr/lib/jvm/java-1.8.0-openjdk/jre/lib/ext/