I've been working with a grails 1.3.7 project within STS for the last few months.
Our test and production environments use JBoss 5.1.
I upgraded our grails app to 2.1.0 recentlly and it all ran ok locally.
Major problems occured when I deployed it to our test environment (Jboss issues).
So in order to avoid this in future I would like to develop locally using JBoss also.
Is there a Eclipse/STS plugin I can use for this?
Thanks
Don't think there's a specific plugin for jboss
Seems your only options now are tomcat and jetty, if you need to stick with the 'run-app' command
If you can give up the debug console and check your test info at the browser, then you can probably write a small script to auto-deploy to a local jboss server, which you can set up through eclipse workspace
Related
Looking for help on the issue that we are facing with the deployment of the war that is generated through maven build. Unable to install or update the application. According to logs the previous application server is not even being stopped though environment properties are being set in the ‘application-config.properties’ file during the deployment process to stop the previous server and start a new one.
If you need more details, please contact us.
Application config specifications:
Combination of struts(version 2.1.8) and spring(version 2.5.6) framework.
Java 1.8 version with web sphere version 6.1 and dynamic web module version 3.1
Maven-compiler-plugin version 3.7.0 and maven-war-plugin 3.2.1.
We have a green-field deployment opportunity, and it seems simple to have grails manage the servlet container for us instead of installing it through the OS package manager.
Understanding that run-app is never suitable for deployment, is run-war a good option?
The usual way to deploy a Grails app to production is to run grails war to build a .war file and deploy that to your container. According to the docs run-war
is useful for quick deployment and/or testing
so on that basis, it seems that it's not intended for production deployments
Is there any way to upgrade project to newer version of Grails from within GGTS ?
Settings at
Window > Preferences > Groovy > Grails
changed settings only to newly created projects. Even if I set the newer version, if I run "grails upgrade" then it wants to upgrade to the older version.
I know, that I could do it from console, however messing with GRAILS_HOME on Windows is not the most pleasurable feeling in the world for me ...
I'm pretty sure that GGTS don't download Grails versions. For Unix based systems you have the great GVM tool, and you can use it on Windows with Cygwin.
If this is not an option to you, there's the Gravy, but be aware that:
Gravy has no intention of competing with GVM and its rich
functionality set. Instead, it only addresses the task of switching
locally present Grails versions within the active command shell.
So it means that you have to manually download the Grails versions, and the bat will handle the switch from one to another.
We have a grails application that we build using hudson. Hudson used to deploy the generated war to tomcat through the tomcat-manager. Now that we are moving to JBoss 7, there is no obvious step available in hudson to deploy to JBoss7. Is there are plugin for JBoss7 deployment that I can use? Or commands to perform deployments on JBoss7?
You should check this out:
https://docs.jboss.org/jbossas/7/plugins/maven/latest/
Also if you prefer to use scripting: https://github.com/maxandersen/as7scripting (it might be a little bit outdated now)
Regards
This has been very upsetting for me up till now. Here is what I am trying to do:
IDE I'm using is Intellij IDEA.
Building a grails application.
Grails application specifies two dependencies on in house grails plugins also being developed in IntelliJ as separate grails plugin projects.
Now to make any changes to plugins, I update the source code in plugin projects and use mavan-install (Maven Publisher plugin) to deploy to local Maven repository.
I have to uninstall the plugin in core grails project. Delete the plugin cache from ivy and then run the core grails project which gets the latest copy of plugin from local maven repository.
What's the effective and ideal way to achieve this? A single change makes me do some 5 minutes of labour work to even test and run core application.
Any recommendations/ best practices?
Use inline plugins for this - see section "Specifying Plugin Locations" in http://grails.org/doc/latest/guide/12.%20Plug-ins.html#12.1%20Creating%20and%20Installing%20Plug-ins
By specifying the plugin project directory with grails.plugin.location.<plugin-name> as the location of the installed plugin, you can edit the real files and the changes will affect the test application, and there's no need to sync anything up.